<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Access on Nalar</title>
    <link>https://nalar.dev/tags/data-access/</link>
    <description>Recent content in Data Access on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/data-access/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keyset Pagination Under Concurrent Writes</title>
      <link>https://nalar.dev/keyset-pagination-under-concurrent-writes/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/keyset-pagination-under-concurrent-writes/</guid>
      <description>&lt;h1 id=&#34;keyset-pagination-under-concurrent-writes&#34;&gt;Keyset Pagination Under Concurrent Writes&lt;/h1&gt;&#xA;&lt;p&gt;A query returns twenty rows ordered by creation time. Before the client asks for the next twenty, another transaction inserts a row near the front of that order. The data set has changed, but the client still expects page two to continue from the point page one reached.&lt;/p&gt;&#xA;&lt;p&gt;That expectation exposes the main difference between offset pagination and keyset pagination. An offset identifies a position in a particular query result. A keyset cursor identifies an ordering boundary. Under concurrent writes, those are not equivalent references.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
