<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Adbc on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/adbc/</link>
    <description>Recent content in Adbc on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/adbc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ADBC vs Arrow Flight SQL vs JDBC in 2026: Stop Copying Rows Between Your Database and Your Pipeline</title>
      <link>https://www.pistack.xyz/posts/2026-10-24-adbc-vs-arrow-flight-sql-vs-jdbc-columnar-connectivity-guide/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-24-adbc-vs-arrow-flight-sql-vs-jdbc-columnar-connectivity-guide/</guid>
      <description>&lt;p&gt;Every analytics pipeline built on a classic driver pays the same tax, and almost nobody measures it. A query returns rows: the driver materialises one Python object (or one JVM object, or one Go struct) per row, your code converts those rows into a columnar frame, and then the frame is serialised again to move to the next process. For a 50-million-row scan, that is three full transpositions of the data — the query itself is often the &lt;em&gt;fast&lt;/em&gt; part.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
