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 conversion policy for the details.
Use it from Python
import sqlquack
result = sqlquack.convert(
sql="SELECT 1 AS total",
options=sqlquack.ConvertOptions(no_config=True),
)
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
| Command | What it does |
|---|---|
make pending DIALECT=snowflake |
What isn't recorded yet, in both suites |
make check-syntax DIALECT=snowflake |
Rerun the parser against recorded evidence (offline) |
make record-syntax DIALECT=duckdb |
Record evidence for new syntax cases |
make check-convert DIALECT=snowflake [CASES=temporal] |
Replay recorded translations on DuckDB (offline) |
make record-convert DIALECT=snowflake |
Record new translation cases on Snowflake |
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.
1 maintainer
Metadata
1 maintainer
Release files for sqlquack-cli 0.4.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 |
|---|---|---|---|---|
| sqlquack_cli-0.4.0.tar.gz | 2.4 MB | With provenance | Details for sqlquack_cli-0.4.0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| sqlquack_cli-0.4.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for sqlquack_cli-0.4.0-py3-none-win_amd64.whl |
| sqlquack_cli-0.4.0-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details for sqlquack_cli-0.4.0-py3-none-manylinux_2_28_x86_64.whl |
| sqlquack_cli-0.4.0-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details for sqlquack_cli-0.4.0-py3-none-manylinux_2_28_aarch64.whl |
| sqlquack_cli-0.4.0-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for sqlquack_cli-0.4.0-py3-none-macosx_11_0_arm64.whl |
| sqlquack_cli-0.4.0-py3-none-macosx_10_15_x86_64.whl | Python 3 | none | macOS 10.15+ x86-64 | Details for sqlquack_cli-0.4.0-py3-none-macosx_10_15_x86_64.whl |
Total release size: 139.1 MB
Release files / sqlquack_cli-0.4.0.tar.gz
| Download URL | sqlquack_cli-0.4.0.tar.gz |
|---|---|
| Size | 2.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65a626067bfd31e41796fbc8a7c266954375c3daecfed34b5bac425db8789000
|
|
BLAKE2b-256 checksum How to use checksums |
46b247c98620c46712329b2c29f6d37705bf06288679e724045fece7ca28e0d1
|
| 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 10, 2026.
Transparency logRelease files / sqlquack_cli-0.4.0-py3-none-win_amd64.whl
| Download URL | sqlquack_cli-0.4.0-py3-none-win_amd64.whl |
|---|---|
| Size | 24.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
af3c913728b4e6c1ac15e7391b29a7d58fc325215a0aaccae8f84d72c0c8183d
|
|
BLAKE2b-256 checksum How to use checksums |
037fa2b13669a26bb02dc1d9e03ccd84542df1dfe31be0cfcca333dbc3336612
|
| 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 10, 2026.
Transparency logRelease files / sqlquack_cli-0.4.0-py3-none-manylinux_2_28_x86_64.whl
| Download URL | sqlquack_cli-0.4.0-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 31.7 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
f8899fb0dcf4f182b2ad03361e9db1bea11224835e3857a88fce6c5b567704b2
|
|
BLAKE2b-256 checksum How to use checksums |
29381a96f9bff1e0f0ad02ea8a9ca7c44fc432177a1f5921d2a5668f3772119b
|
| 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 10, 2026.
Transparency logRelease files / sqlquack_cli-0.4.0-py3-none-manylinux_2_28_aarch64.whl
| Download URL | sqlquack_cli-0.4.0-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 27.7 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
124ab1b0b0553ab8517eaa2e74478c7e7f51030dca4339a1abbf55a41ad54949
|
|
BLAKE2b-256 checksum How to use checksums |
93405ac28720693bfb453b96b9b24f604c7940fd45fbf66e58b33e8e96546d75
|
| 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 10, 2026.
Transparency logRelease files / sqlquack_cli-0.4.0-py3-none-macosx_11_0_arm64.whl
| Download URL | sqlquack_cli-0.4.0-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 25.1 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c597df23dc14cc51b6992c7c759611730211188fb76c4b3f7f094cfd74c6d3c8
|
|
BLAKE2b-256 checksum How to use checksums |
f3eedc400dc9e663e52d0e4e64cdd3df748403a0a5011f05e1dcc8cf6dd3b50a
|
| 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 10, 2026.
Transparency logRelease files / sqlquack_cli-0.4.0-py3-none-macosx_10_15_x86_64.whl
| Download URL | sqlquack_cli-0.4.0-py3-none-macosx_10_15_x86_64.whl |
|---|---|
| Size | 27.5 MB |
| Tags | Python 3 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
691cd177daa17f65962e7977d704c9e754dee66b39a518b1fe85dea6bf15b54d
|
|
BLAKE2b-256 checksum How to use checksums |
c03a7350776f0b4b0d3fd516807cb219a48aee9b73d76768635b3ab31b93b0bf
|
| 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 10, 2026.
Transparency logSecurity for sqlquack-cli 0.4.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
All 6 files in this release have been uploaded with provenance metadata.
Attestation for sqlquack_cli-0.4.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 10, 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.
