<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Schema Design on Nalar</title>
    <link>https://nalar.dev/tags/schema-design/</link>
    <description>Recent content in Schema Design on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/schema-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Derive Row Values in SQLite with Generated Columns</title>
      <link>https://nalar.dev/derive-row-values-in-sqlite-with-generated-columns/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/derive-row-values-in-sqlite-with-generated-columns/</guid>
      <description>&lt;p&gt;Applications often store values that can be calculated from other columns: an order-line total from quantity and unit price, a normalized search key from text, or a duration from two timestamps. The tempting approach is to calculate the value in application code and save both the inputs and the result.&lt;/p&gt;&#xA;&lt;p&gt;That creates two sources of truth. If one code path updates the inputs but forgets to update the derived value, the row becomes internally inconsistent.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
