<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>KvSQL on SoftDevStudio.com</title>
    <link>https://softdevstudio.com/tags/kvsql/</link>
    <description>Recent content in KvSQL on SoftDevStudio.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://softdevstudio.com/tags/kvsql/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KvSQL Joins the Studio With an Embedded Engine and a Server Where Key Reads Skip SQL</title>
      <link>https://softdevstudio.com/kvsql-joins-the-studio-with-an-embedded-engine-and-a-server-where-key-reads-skip-sql/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/kvsql-joins-the-studio-with-an-embedded-engine-and-a-server-where-key-reads-skip-sql/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://kvsql.com/&#34;&gt;KvSQL&lt;/a&gt; is the studio&amp;rsquo;s twenty-seventh project, and its first database in Rust. It keeps one copy of the data for two kinds of access. A row read by its key comes straight from the storage tree, with nothing parsed or planned. SQL about the same rows goes through the parser and reads the same bytes. One transaction covers both, and secondary indexes stay right whichever door wrote the row. &lt;a href=&#34;https://kvsql.com/why-key-lookups-and-sql-belong-on-the-same-records/&#34;&gt;Why that matters&lt;/a&gt;: programs that run a key-value store beside SQLite keep two copies in step and can&amp;rsquo;t commit across them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
