<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sqldelight on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sqldelight/</link>
    <description>Recent content in Sqldelight on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sqldelight/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kotlin Database Libraries in 2026: Exposed vs SQLDelight vs Ktorm — Which One Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-20-kotlin-database-libraries-exposed-sqldelight-ktorm-comparison/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-20-kotlin-database-libraries-exposed-sqldelight-ktorm-comparison/</guid>
      <description>&lt;p&gt;Your Kotlin service works, your SQL is fine, and yet every &lt;code&gt;ResultSet&lt;/code&gt; you unwrap by hand is a small tax you keep paying. The three libraries people actually reach for — JetBrains&amp;rsquo; Exposed, Cash App&amp;rsquo;s SQLDelight, and Ktorm — represent three genuinely different philosophies about who owns your SQL: the Kotlin compiler, the build plugin, or you. Choosing wrong means months of fighting generated code you cannot edit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
