<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Isolation on Nalar</title>
    <link>https://nalar.dev/tags/isolation/</link>
    <description>Recent content in Isolation on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/isolation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Write Skew and Transaction Isolation</title>
      <link>https://nalar.dev/understanding-write-skew-and-transaction-isolation/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/understanding-write-skew-and-transaction-isolation/</guid>
      <description>&lt;p&gt;Transaction isolation is often explained with dirty reads and lost updates, but another anomaly is especially important for multi-row business rules: write skew.&lt;/p&gt;&#xA;&lt;p&gt;Write skew occurs when concurrent transactions read the same valid state, make decisions independently, and update different rows in a way that produces an invalid combined state. Because they do not overwrite the same row, ordinary write-conflict detection may not stop them.&lt;/p&gt;&#xA;&lt;h2 id=&#34;a-simple-invariant&#34;&gt;A simple invariant&lt;/h2&gt;&#xA;&lt;p&gt;Imagine an on-call table where at least one doctor must remain available:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
