← All database systems

CnosDB has no testing implementation in the main SQLancer repository. SQLancer is credited with 7 bugs in it, reported between 2023-06-14 and 2026-04-26. Its source is at cnosdb/cnosdb.

A further 1 report was filed and rejected by the developers as invalid or duplicate. Those are kept in the dataset for transparency and are excluded from every count here.

How the project uses SQLancer

Official testing

The CnosDB project maintains its own SQLancer fork, 3 commit(s) ahead of upstream, last updated 2024-06-28.

SQLancer](https://github.com/sqlancer/sqlancer)作为支持。
README_CN.md in the CnosDB repository.
README_CN.md last verified 2026-09-13
CnosDB 2.0's bug detection is powered by [SQLancer](https://github.com/sqlancer/sqlancer).
README.md in the CnosDB repository.
README.md last verified 2026-09-13
cnosdb/sqlancer is a fork of sqlancer/sqlancer under the CnosDB project's own GitHub organisation, 3 commit(s) ahead of upstream.
/github.com/cnosdb/sqlancer last verified 2026-09-13

How the bugs break down

By year reported

2023
2
2024
2
2026
1
Year not recorded
2

Who found them

Found by the SQLancer project
1
Found by someone outside the project
4
Reporter not recorded
2

By status

Fixed
6
Open
1

By symptom

Unclassified
7

By technique

Technique not recorded
5
Non-optimizing Reference Engine Construction (NoREC)
2

Why each bug counts

The reproducer carries SQLancer's generated schema
5
Listed in the project's own bug repository
2

Who reported them (2)

Benxiaohai001
4
mrigger
1

Every bug on record (8)

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.