<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>pgx on krtffl.dev</title>
    <link>https://krtffl.dev/tags/pgx/</link>
    <description>Recent content in pgx on krtffl.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© [krtffl](https://krtffl.dev)</copyright>
    <lastBuildDate>Mon, 24 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://krtffl.dev/tags/pgx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>sqlc &#43; pgx over an orm: type-safe sql that fails at compile time</title>
      <link>https://krtffl.dev/posts/sqlc-vs-orm-in-go/</link>
      <pubDate>Mon, 24 Nov 2025 00:00:00 +0000</pubDate>
      
      <guid>https://krtffl.dev/posts/sqlc-vs-orm-in-go/</guid>
      <description>&lt;p&gt;the endpoint was slow and i couldn&amp;rsquo;t tell you which query to blame, because i hadn&amp;rsquo;t written any. that&amp;rsquo;s the deal you sign with a reflection-based orm: you describe some structs, you call &lt;code&gt;db.Preload(&amp;quot;Photos&amp;quot;).Find(&amp;amp;pets)&lt;/code&gt;, and somewhere behind the curtain the library assembles sql you never see, fires off a number of round trips you never counted, and hands you back objects. when it&amp;rsquo;s fast, it&amp;rsquo;s lovely. when it&amp;rsquo;s slow, you&amp;rsquo;re debugging a library&amp;rsquo;s imagination.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
