One line · Every ADBC language

    Install GizmoData’s ADBC drivers

    One command installs a driver for every ADBC driver manager on your computer: Python, Go, Rust, R and C/C++ then load it by name. No sudo, and no vendor client libraries.

    Choose a driver

    Run the line for your system in a terminal. The macOS and Linux line works in any POSIX shell; the Windows line runs in PowerShell 5.1 or 7. Each installs the latest release.

    Apache-2.0

    Hardcharger, GizmoData’s DuckDB 2.0 server, over Chargewire, with its query tags, session settings and browser sign-in.

    Linux x86-64 and arm64, macOS on Apple silicon and Intel, Windows x64 and Arm64

    macOS and Linux
    curl https://install.adbc.gizmodata.com/hardcharger | sh
    Windows (PowerShell)
    irm https://install.adbc.gizmodata.com/hardcharger.ps1 | iex
    Python only, with pip
    pip install adbc-driver-hardcharger
    Apache-2.0

    Any server that speaks Chargewire, the open HTTP protocol with Apache Arrow results.

    Linux x86-64 and arm64, macOS on Apple silicon and Intel, Windows x64 and Arm64

    macOS and Linux
    curl https://install.adbc.gizmodata.com/chargewire | sh
    Windows (PowerShell)
    irm https://install.adbc.gizmodata.com/chargewire.ps1 | iex
    Python only, with pip
    pip install adbc-driver-chargewire
    Apache-2.0

    GizmoSQL servers, over Apache Arrow Flight SQL, with OAuth/SSO and automatic DDL/DML detection.

    Linux x86-64 and arm64, macOS on Apple silicon and Intel, Windows x64 and Arm64

    macOS and Linux
    curl https://install.adbc.gizmodata.com/gizmosql | sh
    Windows (PowerShell)
    irm https://install.adbc.gizmodata.com/gizmosql.ps1 | iex
    Python only, with pip
    pip install adbc-driver-gizmosql

    Oracle Database, over Oracle’s own TNS/TTC wire protocol. No Oracle Client libraries: no Instant Client, no ORACLE_HOME, no LD_LIBRARY_PATH.

    Linux x86-64 and arm64, macOS on Apple silicon, Windows x64 and Arm64

    macOS and Linux
    curl https://install.adbc.gizmodata.com/oracle | sh
    Windows (PowerShell)
    irm https://install.adbc.gizmodata.com/oracle.ps1 | iex
    Python only, with pip
    pip install adbc-driver-oracle
    MIT

    IBM Db2, over the DRDA wire protocol. No IBM CLI or ODBC driver, no db2jcc.

    Linux x86-64 and arm64, macOS on Apple silicon, Windows x64

    macOS and Linux
    curl https://install.adbc.gizmodata.com/db2 | sh
    Windows (PowerShell)
    irm https://install.adbc.gizmodata.com/db2.ps1 | iex
    Python only, with pip
    pip install adbc-driver-db2

    A remote DuckDB 2.0, over DuckDB’s Quack protocol. No DuckDB library on the client.

    Linux x86-64 and arm64, macOS on Apple silicon, Windows x64 and Arm64

    macOS and Linux
    curl https://install.adbc.gizmodata.com/quack | sh
    Windows (PowerShell)
    irm https://install.adbc.gizmodata.com/quack.ps1 | iex
    Python only, with pip
    pip install adbc-driver-quack

    Not sure of the name? The address without a driver prints the list:

    curl https://install.adbc.gizmodata.com | sh

    Load it by name, from any language

    After the install, the driver’s name is all a driver manager needs. These examples load the Hardcharger driver and run a query against a local Hardcharger server; for another driver, change the name and the connection options.

    pip install adbc-driver-manager pyarrow
    1import adbc_driver_manager.dbapi as dbapi
    2
    3with dbapi.connect(
    4    driver="hardcharger",
    5    db_kwargs={
    6        "uri": "hardcharger://localhost?tls=false",
    7        "username": "hardcharger",
    8        "password": "change-me",
    9    },
    10) as conn:
    11    with conn.cursor() as cur:
    12        cur.execute(operation="SELECT 42 AS answer")
    13        print(cur.fetchone())  # (42,)

    In C, set the load flags to ADBC_LOAD_FLAG_DEFAULT as above: without them the driver manager does not search the drivers directories. The server for these examples is one line too:

    Versions, options and uninstall

    Set an environment variable for the script, or pass options after sh -s --. In PowerShell, set the variable with $env: before the irm line (it stays set for the rest of that PowerShell session), or run the script as a script block and pass parameters, as the uninstall line below does.

    Pin a version
    curl https://install.adbc.gizmodata.com/hardcharger | ADBC_VERSION=2.6.1 sh
    # or
    curl https://install.adbc.gizmodata.com/hardcharger | sh -s -- --version 2.6.1
    $env:ADBC_VERSION = '2.6.1'; irm https://install.adbc.gizmodata.com/hardcharger.ps1 | iex
    Uninstall
    curl https://install.adbc.gizmodata.com/hardcharger | sh -s -- --uninstall
    & ([scriptblock]::Create((irm https://install.adbc.gizmodata.com/hardcharger.ps1))) -Uninstall
    shPowerShellEnvironmentWhat it does
    --version <v>-Version <v>ADBC_VERSIONA release, 1.2.3 or v1.2.3. The default is the latest release.
    --dir <dir>-Dir <dir>ADBC_DIRInstall into this drivers directory instead of your own (for example one on ADBC_DRIVER_PATH).
    --system—ADBC_SYSTEM=1Install into the system-wide drivers directory (may need sudo). Not on Windows, where the system level is the registry.
    --name <name>-Name <name>ADBC_NAMEInstall under another name, side by side with another driver of the same name.
    --archive <file>-Archive <file>ADBC_ARCHIVEInstall a library archive you already have; nothing is downloaded.
    --base-url <url>-BaseUrl <url>ADBC_BASE_URLDownload the release files from a mirror.
    --uninstall-UninstallADBC_UNINSTALL=1Remove the driver: its manifest and its directory, nothing else.

    What gets installed, and where

    • The driver’s shared library, with its license, from the driver’s GitHub release, in a folder named for its version. Installing another version replaces it.
    • A driver manifest, <name>.toml, with the library’s full path and its entry point. ADBC driver managers look for it when you ask for a driver by name.
    • Nothing else: no PATH changes, no shell startup files, no registry entries.
    SystemYour drivers (the default)System-wide (--system)
    Linux$XDG_CONFIG_HOME/adbc/drivers (~/.config/adbc/drivers)/etc/adbc/drivers
    macOS~/Library/Application Support/ADBC/Drivers/Library/Application Support/ADBC/Drivers
    Windows%LOCALAPPDATA%\ADBC\Drivers—

    The Hardcharger driver on a Mac

    ~/Library/Application Support/ADBC/Drivers/
    ├── hardcharger.toml
    └── hardcharger/
        ├── .adbc-install
        └── 2.6.1/
            ├── libadbc_driver_hardcharger.dylib
            ├── LICENSE
            ├── THIRD_PARTY_NOTICES
            └── hardcharger.toml.in

    Its manifest, hardcharger.toml

    # Written by https://install.adbc.gizmodata.com (https://github.com/gizmodata/adbc-install).
    # Load it by name: driver = "hardcharger" in any ADBC driver manager.
    manifest_version = 1
    
    name = 'Hardcharger'
    version = '2.6.1'
    publisher = 'GizmoData'
    license = 'Apache-2.0'
    url = 'https://github.com/gizmodata/hardcharger-adbc'
    
    [ADBC]
    version = '1.1.0'
    
    [Driver]
    entrypoint = 'AdbcDriverHardchargerInit'
    
    [Driver.shared]
    macos_arm64 = "/Users/you/Library/Application Support/ADBC/Drivers/hardcharger/2.6.1/libadbc_driver_hardcharger.dylib"

    Another driver with the same name

    If another vendor’s driver already uses the name, ours replaces it. Its manifest is kept, renamed to <name>.toml.replaced-<time>, and the installer prints the command that puts it back. To keep both, install ours under another name:

    curl https://install.adbc.gizmodata.com/hardcharger | sh -s -- --name gizmodata-hardcharger

    Checked before it’s installed

    Checksums

    Every archive is checked against the release’s SHA256SUMS, or the archive’s own .sha256 file. A missing or different checksum stops the install.

    The right build

    The installer picks the library for your system and processor, including Apple silicon under Rosetta. Linux needs glibc: Alpine and other musl systems are refused with a clear message.

    Never half-written

    The manifest is written to a temporary file and moved into place in one step, so a driver manager never reads half of one.

    Install FAQ

    How do I install a GizmoData ADBC driver?

    On macOS or Linux run curl https://install.adbc.gizmodata.com/hardcharger | sh, and on Windows run irm https://install.adbc.gizmodata.com/hardcharger.ps1 | iex in PowerShell, with hardcharger replaced by the driver you want: hardcharger, chargewire, gizmosql, oracle, db2 or quack. No sudo is needed. The driver goes into your own ADBC drivers directory with a driver manifest, so every ADBC driver manager on the machine loads it by name.

    Does the Oracle driver need Oracle Client libraries?

    No. The Oracle driver speaks Oracle’s TNS/TTC wire protocol itself, in pure Go: no Instant Client, no ORACLE_HOME, no LD_LIBRARY_PATH. It is an independent implementation, not affiliated with or endorsed by Oracle.

    Which languages can use the drivers?

    Any language with an ADBC driver manager that reads driver manifests, including Python (adbc-driver-manager), Go (drivermgr), Rust (adbc_driver_manager), R (adbcdrivermanager) and C/C++ (libadbc_driver_manager). Each finds the driver by its name, for example driver = "hardcharger".

    How are the drivers licensed?

    The Hardcharger, Chargewire and GizmoSQL drivers are Apache-2.0; the Oracle, Db2 and DuckDB Quack drivers are MIT-licensed. All six are open source on GitHub.

    How do I install a specific version?

    Set ADBC_VERSION, for example curl https://install.adbc.gizmodata.com/hardcharger | ADBC_VERSION=2.6.1 sh, or pass --version 2.6.1 after sh -s --. In PowerShell, set $env:ADBC_VERSION first. The default is the latest release.

    What if another driver with the same name is already installed?

    The installer replaces it, after moving that driver’s manifest aside to <name>.toml.replaced-<time>. It prints what it replaced and the command that puts it back. To keep both, install ours under another name with --name.

    Is the download verified?

    Yes. The installer checks the library archive against the release’s SHA256SUMS (or the archive’s own .sha256 file) and refuses to install when the checksum is missing or doesn’t match.

    How do I uninstall a driver?

    Run the same line with --uninstall: curl https://install.adbc.gizmodata.com/hardcharger | sh -s -- --uninstall. It removes the driver’s manifest and its directory and nothing else. In PowerShell, run the script with -Uninstall: & ([scriptblock]::Create((irm https://install.adbc.gizmodata.com/hardcharger.ps1))) -Uninstall.

    Now connect to a server

    Hardcharger on GizmoData Cloud is a managed DuckDB 2.0 server in one click on AWS, Google Cloud or Azure, ready for the Hardcharger and Chargewire drivers.

    Run it on GizmoData Cloud

    Oracle is a registered trademark of Oracle and/or its affiliates. IBM and Db2 are trademarks of International Business Machines Corporation. DuckDB is a trademark of the DuckDB Foundation. GizmoData’s drivers are independent implementations, not affiliated with or endorsed by these companies.

    Schedule a demo!powered by Calendly