Database · native ODBC

DuckDB into Apache Arrow with ADBC

DuckDB (latest), read and written through adbcBridge — the ADBC driver that loads the database's ODBC driver — verified on Linux, macOS arm64 and Windows x64. Everything below is the compatibility matrix's record for this row.

Status

Linux✓ pass

PASS

macOS arm64✓ pass

PASS (DuckDB ODBC 1.5.5.0, universal binary)

Windows x64✓ pass

PASS (duckdb_odbc 1.5.5.0, DuckDB Driver registered by the zip's odbc_install.exe)

Driver and connection string

ODBC driver: duckdb-odbc
Wire: native ODBC
adbcBridge: 0.1.1 (release)

The connection string the matrix used, as the connection strings reference records it (File-based (no server)); {drv} is the driver library or its name from odbcinst.ini, and the host, port and credentials are the test server's.

Driver={drv};Database=<path>/duck.db;

Python

import adbcbridge

# {drv}: the ODBC driver library (path), or its name from odbcinst.ini
conn = adbcbridge.connect(uri="Driver={drv};Database=<path>/duck.db;")
with conn.cursor() as cur:
    cur.execute("SELECT * FROM my_table")
    table = cur.fetch_arrow_table()      # pyarrow.Table

Polars and pandas

import polars as pl, pandas as pd

df = pl.read_database("SELECT * FROM my_table", connection=conn)   # Polars, Arrow-native
pdf = pd.read_sql("SELECT * FROM my_table", conn)                   # pandas 2.2+, ADBC connection

pip install adbcbridge brings the driver library; the DuckDB ODBC driver is installed the way its vendor documents, then named in Driver=. Rust, Go, C# and Java use the same connection string through their ADBC driver managers — see the docs.

What the matrix recorded

driver quirks handled: 2048-row vectors (the driver writes a full vector into bound buffers whatever the rowset size), no SQL_BIT params (booleans go as integers), no usable parameter arrays