← All database systems

StoneDB has no testing implementation in the main SQLancer repository. SQLancer is credited with 16 bugs in it, reported between 2023-07-03 and 2023-07-29. Its source is at stoneatom/stonedb.

How the bugs break down

By year reported

2023
12
Year not recorded
4

Who found them

Found by the SQLancer project
12
Reporter not recorded
4

By status

Fixed
3
Open
13

By symptom

Unclassified
16

By technique

Technique not recorded
16

Why each bug counts

The reproducer carries SQLancer's generated schema
10
Listed in the project's own bug repository
4
Filed by someone who runs SQLancer campaigns
2

Who reported them (1)

zhenglin-charlie-li
12

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.

Reported Report Status Technique Reporter
2023-07-29 bug: can not build from source code when following the doc open zhenglin-charlie-li
2023-07-19 crash: StoneDB crash: PRIMARY KEY, HAVING, IS NULL open zhenglin-charlie-li
2023-07-19 crash: StoneDB crash: HAVING, IS NULL open zhenglin-charlie-li
2023-07-19 bug: query result wrong: SELECT open zhenglin-charlie-li
2023-07-19 bug: query result wrong: NATURAL LEFT JOIN open zhenglin-charlie-li
2023-07-19 bug: query result wrong: INSERT, DELETE, UNION ALL open zhenglin-charlie-li
2023-07-19 bug: query result wrong: CASE WHEN THEN ELSE open zhenglin-charlie-li
2023-07-19 bug: query result wrong: ALTER, DEFAULT open zhenglin-charlie-li
2023-07-18 crash: StoneDB crash when executing the right shift operator open zhenglin-charlie-li
2023-07-16 bug: expected supported SQL sytax not support (UNION ALL, LIKE) open zhenglin-charlie-li
2023-07-14 crash: StoneDB crash when executing the command (SELECT, HAING, GROUP BY, IS NULL) fixed zhenglin-charlie-li
2023-07-03 bug: docker image stoneatom/stonedb:v1.0.4 is too large, is this expected? fixed zhenglin-charlie-li
crash: StoneDB crash: SUM open
bug: query result not correct fixed
bug: bad dpn index when deleting rows open
bug: after altering operation, `NULL` values is evlauated to be `TRUE` in StoneDB open

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.