sqlalchemy-adbc
Generic SQLAlchemy dialect for any Apache Arrow ADBC driver — so any tool that speaks SQLAlchemy (pandas, marimo, Superset, dbt, Polars) can read and write against Flight SQL, PostgreSQL, SQLite, Snowflake, and BigQuery through the Arrow-native wire path.
Why this exists
ADBC drivers speak Python DBAPI and return results as Arrow record batches —
zero per-row materialization, no driver-specific JDBC/ODBC install. But most
of the Python ecosystem wires into databases through SQLAlchemy, and ADBC
doesn't ship a dialect. This package is a thin translation layer: SQLAlchemy
URL → ADBC db_kwargs → DBAPI connection.
Install
pip install sqlalchemy-adbc
# With a driver extra:
pip install "sqlalchemy-adbc[flightsql]"
pip install "sqlalchemy-adbc[postgresql]"
pip install "sqlalchemy-adbc[sqlite]"
pip install "sqlalchemy-adbc[snowflake]"
pip install "sqlalchemy-adbc[bigquery]"
Quickstart
import sqlalchemy
# Flight SQL
engine = sqlalchemy.create_engine(
"flightsql+adbc://flight-sql.example.com:443?tls=true",
connect_args={"db_kwargs": {
"adbc.flight.sql.authorization_header": f"Bearer {token}",
}},
)
# SQLite
engine = sqlalchemy.create_engine("sqlite+adbc:///path/to/db.sqlite")
# PostgreSQL
engine = sqlalchemy.create_engine(
"postgresql+adbc://user:pass@host:5432/mydb"
)
# Works with pandas, Polars, marimo SQL cells, etc.
import pandas as pd
df = pd.read_sql("SELECT 1 AS n", engine)
URL forms
URLs follow SQLAlchemy's <backend>+<driver>:// convention, with adbc
as the driver. The pre-0.4 adbc+<backend>:// spelling still works but
emits a DeprecationWarning and will be removed in 1.0.
| Backend | URL |
|---|---|
| Flight SQL | flightsql+adbc://host:port?tls=true&authorization=... |
| Flight SQL | flightsql+adbc://user:TOKEN@host:port?tls=true (bearer) |
| PostgreSQL | postgresql+adbc://user:pass@host:port/database |
| SQLite | sqlite+adbc:///path/to/db or sqlite+adbc:///:memory: |
| Snowflake | snowflake+adbc://user:pass@account/db/schema?warehouse=W |
| BigQuery | bigquery+adbc:///my-project?dataset=my_dataset |
Flight SQL query-string options
| Key | Meaning |
|---|---|
tls=true |
Use grpc+tls:// instead of grpc:// |
authorization=... |
Sets the ADBC AUTHORIZATION_HEADER db_kwarg |
header.<name>=<v> |
Forwarded via ADBC's RPC_CALL_HEADER_PREFIX |
| (any other key) | Passed through as a db_kwarg verbatim |
Proxies
The Flight SQL, Snowflake and BigQuery drivers are Go libraries that read
HTTP_PROXY, HTTPS_PROXY and NO_PROXY (either case) from the process
environment, so if those are set nothing more is needed. When they are not,
a [proxy] section in the local config file (below) is exported into the
environment on the first connect. A variable you already set always wins;
the export is process-wide because that is the only lever the drivers have.
PostgreSQL (libpq) and SQLite have no HTTP proxy concept.
Authentication
Pick a mode with auth= in the URL, or name a profile from the config file
with auth_profile=:
| Mode | Flight SQL | Snowflake | Credentials |
|---|---|---|---|
bearer |
default | – | URL password is the token (flightsql+adbc://u:TOKEN@host) |
basic |
yes | default | URL user:password@; Flight SQL uses the Handshake |
negotiate |
yes | – | Kerberos/SPNEGO via pip install "sqlalchemy-adbc[kerberos]"; SPN is HTTP@<host> unless a profile pins spn |
oauth2 |
yes | yes | client credentials: oauth2_token_url=, URL client_id:client_secret@ (or a profile); optional oauth2_scope=, oauth2_audience= |
Flight SQL runs the OAuth2 flow inside the driver and refreshes tokens
itself. Snowflake receives a token minted by this package per connection.
Snowflake's own authenticator= DSN options (key pair, Okta, external
browser) keep working unchanged through the query string.
Config file
Secrets stay out of URLs by living in a profile. The file is read from
$SQLALCHEMY_ADBC_CONFIG, else ~/.config/sqlalchemy-adbc/config.toml;
it must be owned by you and not group- or world-writable, and the working
directory is deliberately never searched. Any value may be env:NAME.
[proxy]
https_proxy = "http://proxy.corp.example:3128"
no_proxy = "localhost,127.0.0.1,.corp.example"
[auth.drls-flight]
type = "oauth2"
token_url = "https://keycloak.example/realms/drls/protocol/openid-connect/token"
client_id = "marimo"
client_secret = "env:DRLS_FLIGHT_CLIENT_SECRET"
scope = "openid"
[auth.corp-kerberos]
type = "negotiate"
spn = "HTTP@flight-sql.corp.example"
engine = sqlalchemy.create_engine(
"flightsql+adbc://flight-sql.corp.example:443?auth_profile=drls-flight"
)
A URL that names a profile may only adjust oauth2_scope and
oauth2_audience; the token endpoint, SPN and client identity stay under
the config owner's control, env: references resolve only from the file,
and oauth2_client_secret is never accepted in a query string.
Status
Beta. Core dialect + reflection + Alembic autogenerate work on the ADBC drivers we exercise in CI (SQLite end-to-end, PostgreSQL via service container). Not 1.0 yet — we want a few months of real-world use and at least one release without breaking changes before committing to a stable API.
Full history in CHANGELOG.md. Download tags on GitHub Releases; published wheels on PyPI.
What works
SELECT/INSERT/CREATE TABLE/DROP TABLE/ALTER TABLEfor every advertised driverMetaData.reflect(bind=engine)— full Inspector contract backed by ADBCGetObjects, including columns, PK, FK, unique constraints, indexes (native PRAGMA /pg_catalogqueries on SQLite and PG)- Alembic
autogenerate— end-to-end, reusing SQLAlchemy's native backend DDL impls via standard dialect-name lookup - URL forms for Flight SQL, PostgreSQL, SQLite, Snowflake, BigQuery with correct special-character escaping in passwords
- PostgreSQL typed decorators: JSONB / JSON / UUID / INET / CIDR /
MACADDR, and all range and multirange types (
int4range…tstzmultirange) plushstore, returning SQLAlchemy's ownRange/MultiRange/dictwith working@>,&&,?operators and reflection
Known limitations
- Raw SQL readers see PostgreSQL range / hstore values as bytes —
pd.read_sql("SELECT period FROM t", engine)and SQL Lab style queries carry no column type information, so the ADBC binary form reaches Python untouched. Typed columns via Core, ORM or reflection are decoded (#11) - Drivers exercised in CI — SQLite fully, PostgreSQL integration-tested via service container. Snowflake / BigQuery / Flight SQL inherit the shared reflection path but have no per-driver CI (#12)
- ADBC SQLite NOT NULL reporting — fixed upstream in
adbc_driver_sqlite1.13 (Python ≥ 3.11). On older drivers every column reflects as nullable=True (#13)
Tests: 238 passing on Python 3.10–3.13, including 25 PostgreSQL integration tests against a service-container Postgres.
Development
git clone https://github.com/drls-io/sqlalchemy-adbc
cd sqlalchemy-adbc
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest # unit tests; live backends via DRLS_PG_URL / DRLS_SNOWFLAKE_URL
ruff check src/ tests/ && ruff format --check src/ tests/
mypy src tests
tox # same gates across Python 3.10–3.13 × SQLAlchemy 2.0/2.1 (tox.ini)
Releasing
Publishing is automated via PyPI trusted publishing
(OIDC, no API tokens). One-time setup on pypi.org: add a pending publisher
for project sqlalchemy-adbc, owner drls-io, repository sqlalchemy-adbc,
workflow publish.yml, environment pypi. Same for TestPyPI if you want
dry-runs.
Cutting a release:
# 1. Bump version in pyproject.toml
# 2. Commit, tag, push
git commit -am "chore: release v0.1.1"
git tag v0.1.1
git push && git push --tags
The Publish to PyPI workflow fires on the tag, builds sdist+wheel, and
uploads to pypi.org. For TestPyPI dry-runs use workflow_dispatch with
target testpypi.
License
Apache-2.0. See LICENSE.
Metadata
Release files for sqlalchemy-adbc 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sqlalchemy_adbc-0.5.0.tar.gz | 73.6 kB | With provenance | Details for sqlalchemy_adbc-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sqlalchemy_adbc-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for sqlalchemy_adbc-0.5.0-py3-none-any.whl |
Total release size: 119.3 kB
Release files / sqlalchemy_adbc-0.5.0.tar.gz
| Download URL | sqlalchemy_adbc-0.5.0.tar.gz |
|---|---|
| Size | 73.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0e7d12b04e19ec78b7a68230fd12fbdfe2e0f0affdaa45cdc5956f71e6fd6f5
|
|
BLAKE2b-256 checksum How to use checksums |
1eb0cf93e01e4cdc21015e577898115e5b9359fbb8fe410c987c753ce54a9828
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 7, 2026.
Transparency logRelease files / sqlalchemy_adbc-0.5.0-py3-none-any.whl
| Download URL | sqlalchemy_adbc-0.5.0-py3-none-any.whl |
|---|---|
| Size | 45.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93a1c4a99949c32f57d0f67cad89a5af3da3dc38e8fe4aa928d3f310f7015cf0
|
|
BLAKE2b-256 checksum How to use checksums |
dfb1c08b1a2791ac8b2ea6732bb5fd7484dc908da149761bc6392ed8372e6c7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 7, 2026.
Transparency logSecurity for sqlalchemy-adbc 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for sqlalchemy_adbc-0.5.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.