What is adbc-driver-quack?

DuckDB is a fast, embedded database popular with data engineers and analysts. One of its features is the Quack protocol, a way to run a DuckDB instance as a remote server that other programs can connect to over the network. This project, adbc-driver-quack, is a driver that lets you connect to that remote DuckDB server using a standard called ADBC (Apache Arrow Database Connectivity). ADBC matters because it is designed specifically to return data in Apache Arrow format, a column oriented, in memory data layout that moves large datasets between tools without copying or converting them. That means query results arrive as Arrow RecordBatches, which you can immediately hand to data tools that understand Arrow natively, such as Polars, Pandas, or DuckDB running in a local process, all without an expensive serialization step in between. In practice: you start a DuckDB session on a server, install and load the Quack extension, and call one command to make it listen on a port. You then connect from your Python or Go code using a URI like quack://localhost:9494 plus a secret token, and run SQL queries whose results come back as Arrow tables. For large datasets, a streaming mode lets you process one small batch at a time, roughly 2,000 rows per batch, so memory usage stays bounded regardless of result size. You can also push data into the remote DuckDB: the driver supports a bulk ingest path that creates or appends to tables from Arrow data you already have in memory. Available as a Python pip package, supporting macOS, Linux, and Windows on x64 and arm64, and as a Go module. Currently alpha, version 0.1.0-alpha.1. The full README is longer than what was shown.