← Bugs over time
SQLancer is credited with 224 bugs reported in
2022, across 10 database
systems, between 2022-01-10 and
2022-12-28.
A further 29 reports were
filed that year and rejected by the developers as invalid or duplicate;
those are kept in the dataset and counted nowhere.
Which systems (10)
- StarRocks
-
119
- CockroachDB
-
34
- SQLite
-
22
- YugabyteDB
-
16
- MatrixOne
-
9
- TiDB
-
8
- DuckDB
-
7
- Databend
-
4
- QuestDB
-
3
- ClickHouse
-
2
Each system's own page carries its whole history rather than this year's
share: StarRocks, CockroachDB, SQLite, YugabyteDB, MatrixOne, TiDB, and 4 more.
How they break down
Who found them
- Found by the SQLancer project
-
41
- Found by someone outside the project
-
183
By status
- Fixed
-
204
- Confirmed
-
3
- Open
-
17
By symptom
- Unclassified
-
224
By technique
- Technique not recorded
-
187
- Ternary Logic Partitioning (TLP)
-
30
- Non-optimizing Reference Engine Construction (NoREC)
-
7
Why each bug counts
- The reproducer carries SQLancer's generated schema
-
183
- The report names a SQLancer oracle
-
25
- The report names SQLancer
-
13
- Filed by someone who runs SQLancer campaigns
-
3
Who reported them
- wanpengfei-git
-
53
- bajinsheng
-
38
- dulong41
-
29
- cockroach-teamcity
-
24
- qvad
-
14
- yongbingwang
-
10
- iamlinjunhong
-
9
- colorfulu
-
8
Every bug reported in 2022 (253)
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.