sqlquack-cli 0.5.1

_{by SQLStack}

Run warehouse SQL locally.

Translate warehouse SQL into DuckDB SQL for local testing and CI - without a running warehouse.
Website · Docs · Playground · Quickstart

Why SQLQuack?

SQL that runs on two engines doesn't always return the same answer. NULLs, decimal arithmetic and casts can behave differently.

SQLQuack checks its conversion rules against real results from the source warehouse. It handles those differences deliberately and gives you precise diagnostics when it can't convert a query - not plausible-looking SQL and crossed fingers.

• Check early. Catch invalid SQL before it reaches the warehouse.
• Test locally. Convert queries to DuckDB SQL for tests against small fixtures.
• See what's blocking you. Scan a SQL project to find what converts and what needs attention.
• Choose what to accept. Allow or refuse each known difference in sqlquack.toml.

Get started

pip install sqlquack

# Convert your first query
echo "SELECT 1 AS total" | sqlquack convert --no-config

# Check a SQL file
sqlquack check query.sql

# Convert a query using the tables in sources/*.yml
sqlquack convert query.sql

Or try the playground - no installation needed.

See the supported dialects and coverage, project guide and defaults for known differences for the details.

Use it from Python

import sqlquack

result = sqlquack.convert(
    sql="SELECT 1 AS total",
    options=sqlquack.ConvertOptions(no_config=True),
)

Python API

Running the suites

SQLQuack's parsers and conversion rules are checked against evidence recorded on the real engines. Rerunning it needs no account:

git clone https://github.com/sqlstack-io/sqlquack && cd sqlquack
uv sync
make check-syntax DIALECT=snowflake    # rerun the parser against recorded syntax evidence
make check-convert DIALECT=snowflake   # replay recorded translations on DuckDB

A pull request runs what its changed files need. Documentation and website changes build and check the site. Other changes run make check-merge, the Python tests and the replay. The replay reuses main's judgement for every case whose conversion and recording are unchanged, and replays only the rest. A change under one of the full-replay paths in scripts/replay_scope/constants.py replays every case: the DuckDB pin, the lock files, the replay, comparison and policy crates, the error kinds, CI's toolchain and the evidence pin. A change outside every crate the sqlquack binary is built from replays nothing.

Recording needs the dialect's engine: DuckDB and SQLite record locally, while Snowflake, BigQuery and Databricks need a connection. Recording Snowflake syntax evidence isn't public yet. make help lists every target.

Built in Rust. Free and open source. Apache 2.0.

Part of SQLStack.