Database systems and SQLancer
What is tracked
Three different things are tracked separately here, and it is worth being precise about the difference:
- Supported — the main SQLancer repository ships a testing implementation for the system. 21 systems.
- Bugs found — SQLancer has attributed bugs in the system. 41 systems.
- Uses SQLancer — the system's own developers use or integrate SQLancer. 22 projects.
- Planned adoption — a project has proposed adopting SQLancer but has not yet been shown using it. 9 further projects, listed separately below and counted in nothing above.
Supporting a database system says nothing about whether that project uses SQLancer, so adoption is only recorded when the evidence comes from the project or its developers — a CI job, a test script, project documentation, or a developer saying so themselves.
| How the project uses SQLancer | Projects |
|---|---|
| SQLancer in the project's CI | 1 |
| Project-maintained SQLancer testing | 21 |
| Developer-reported use | 1 |
Every system
One row per system that SQLancer supports, has found a bug in, or that a project has proposed testing with it. Each name links to the system's own page, where the bugs and the adoption evidence are listed in full.
| Database system | Bugs | Supported by SQLancer | Uses SQLancer |
|---|---|---|---|
| DuckDB | 302 | Yes | official testing |
| SQLite | 222 | Yes | — |
| CockroachDB | 202 | Yes | |
| StarRocks | 183 | — | developer use |
| TiDB | 172 | Yes | — |
| Dolt | 167 | — | — |
| MonetDB | 139 | — | official testing |
| CrateDB | 81 | — | — |
| QuestDB | 55 | Yes | — |
| Umbra | 55 | — | — |
| Apache DataFusion | 54 | Yes | official testing |
| YugabyteDB | 54 | Yes | official testing |
| ClickHouse | 48 | Yes | official ciofficial testing |
| MySQL | 43 | Yes | — |
| H2 | 20 | Yes | — |
| Apache Doris | 19 | Yes | |
| Databend | 18 | Yes | official testing |
| PostgreSQL | 18 | Yes | — |
| Turso | 18 | — | official testing |
| Virtuoso | 17 | — | — |
| Citus | 16 | Yes | official testing |
| StoneDB | 16 | — | — |
| Wadjet | 16 | — | official testing |
| MariaDB | 15 | Yes | — |
| Oxla | 12 | — | official testing |
| TDengine | 12 | — | — |
| Firebird | 10 | — | — |
| MatrixOne | 9 | — | — |
| RisingWave | 8 | — | |
| BharatDBMS | 7 | — | |
| CnosDB | 7 | — | official testing |
| Apache Cloudberry | 6 | — | |
| OceanBase | 4 | Yes | official testing |
| Presto | 4 | Yes | |
| SeekDB | 3 | — | official testing |
| CUBRID | 1 | — | — |
| FalkorDB | 1 | — | — |
| Hazelcast | 1 | — | official testing |
| Kyzo | 1 | — | — |
| sparq | 1 | — | official testing |
| TiKV | 1 | — | — |
| Apache Hive | — | Yes | — |
| Apache Spark | — | Yes | — |
| Feldera | — | — | official testing |
| GreptimeDB | — | — | |
| HSQLDB | — | Yes | — |
| Materialize | — | Yes | official testing |
| NoisePage | — | — | official testing |
| SereneDB | — | — | official testing |
| Spice.ai OSS | — | — | |
| Tarantool | — | — | |
| XuGu | — | — | official testing |
| YDB | — | — | official testing |
Planned adoption (9)
Projects whose developers have proposed adopting SQLancer — an open issue, a roadmap entry, a testing plan — without anything yet showing the project running it. An intention is not use, so none of these counts towards the 22 projects that do use it, or towards any figure on the front page. They are kept because a proposal from a project's own developers is worth recording, and because it is the thing to re-check later: some of these will become adoption, and others will not.
| Project | Proposal |
|---|---|
| BharatDBMS | BharatDBPG, owner of the BharatDBMS project, proposed adopting SQLancer; the issue is open. |
| Apache Cloudberry | my-ship-it, contributor of the Apache Cloudberry project, proposed adopting SQLancer; the issue is open. |
| CockroachDB | srosenberg, contributor of the CockroachDB project, proposed adopting SQLancer; the issue is open. |
| Apache Doris | ChaseHuangxu, contributor of the Apache Doris project, proposed adopting SQLancer; the issue is closed. |
| GreptimeDB | J0HN50N133, contributor of the GreptimeDB project, proposed adopting SQLancer; the issue is closed. |
| Presto | tdcmeehan, contributor of the Presto project, proposed adopting SQLancer; the issue is open. |
| RisingWave | lmatz, contributor of the RisingWave project, proposed adopting SQLancer; the issue is open. |
| Spice.ai OSS | digadeesh proposed that the Spice.ai OSS project adopt SQLancer for SQL fuzz testing; the issue is open. This is an intention, not evidence that the project runs SQLancer. |
| Tarantool | ligurio, member of the Tarantool project, proposed adopting SQLancer; the issue is open. |