← All database systems
Wadjet has no testing implementation in the
main SQLancer repository.
SQLancer is credited with 16 bugs in it, reported between 2026-08-24 and
2026-09-03.
Its source is at derekmwright/wadjet.
How the project uses SQLancer
Official testing
The Wadjet project maintains SQLancer testing setup in its own repository (tools/sqlancer/run.sh).
# Usage: tools/sqlancer/run.sh
tools/sqlancer/run.sh in the Wadjet repository invokes SQLancer.tools/sqlancer/run.sh
last verified 2026-09-06
git clone --depth 1 https://github.com/sqlancer/sqlancer.git "$TARGET_DIR"
tools/sqlancer/build.sh in the Wadjet repository invokes SQLancer.tools/sqlancer/build.sh
last verified 2026-09-06
Runbook for wadjet issue #289 ("evaluate SQLancer (TLP/NoREC) against the
tools/sqlancer/README.md in the Wadjet repository invokes SQLancer.tools/sqlancer/README.md
last verified 2026-09-06
fmt.Fprintln(w, "SQLancer triage report")
tools/sqlancer/triage/report.go in the Wadjet repository is part of a SQLancer setup the project maintains.tools/sqlancer/triage/report.go
last verified 2026-09-06
// Package triage classifies SQLancer soak-log output (and the wadjet
tools/sqlancer/triage/classify.go in the Wadjet repository is part of a SQLancer setup the project maintains.tools/sqlancer/triage/classify.go
last verified 2026-09-06
How the bugs break down
Who found them
- Found by someone outside the project
-
16
By symptom
- Unclassified
-
16
By technique
- Ternary Logic Partitioning (TLP)
-
9
- Technique not recorded
-
6
- Non-optimizing Reference Engine Construction (NoREC)
-
1
Why each bug counts
- The report names SQLancer
-
12
- The reproducer carries SQLancer's generated schema
-
4
Who reported them (1)
- derekmwright
-
16
Every bug on record (16)
One row per report, newest first, each linking to the report itself. Rejected
reports are marked and are not part of any count above.
Every figure on this page is computed from
_data/impact/.
The attribution policy
explains what has to be true for a bug to be counted.