← All database systems

sparq has no testing implementation in the main SQLancer repository. SQLancer is credited with 1 bugs in it, reported between 2026-07-11 and 2026-07-11. Its source is at sparq-org/sparq.

How the project uses SQLancer

Official testing

The sparq project maintains SQLancer testing setup in its own repository (research/paper-selection.md).

**Field bar (search-verified).** SQLancer (Rigger & Su): ~196 previously-unknown
research/paper-selection.md in the sparq repository invokes SQLancer.
research/paper-selection.md last verified 2026-09-06
7`) is the first dedicated logic-bug testing paper for SPARQL engines (SQL/Datalog/Cypher are covered by SQLancer/queryFuzz/GDsmith; SPARQL is not).
skills/academic-paper/SKILL.md in the sparq repository states that the project uses SQLancer.
skills/academic-paper/SKILL.md last verified 2026-09-06

How the bugs break down

By year reported

2026
1

Who found them

Found by someone outside the project
1

By status

Fixed
1

By symptom

Unclassified
1

By technique

Non-optimizing Reference Engine Construction (NoREC)
1

Why each bug counts

The report names a SQLancer oracle
1

Who reported them (1)

jeswr
1

Every bug on record (1)

One row per report, newest first, each linking to the report itself. Rejected reports are marked and are not part of any count above.

Reported Report Status Technique Reporter
2026-07-11 [metamorph] shard=demo: 20 TLP/NoREC oracle failure(s) (first seed=0) fixed NOREC jeswr

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.