← All database systems

Firebird has no testing implementation in the main SQLancer repository. SQLancer is credited with 10 bugs in it, reported between 2023-03-12 and 2024-09-02. Its source is at FirebirdSQL/firebird.

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 bugs break down

By year reported

2023
5
2024
4
Year not recorded
1

Who found them

Found by the SQLancer project
10

By status

Fixed
9
Confirmed
1

By symptom

Unclassified
10

By technique

Technique not recorded
10

Why each bug counts

The reproducer carries SQLancer's generated schema
9
Filed by someone who runs SQLancer campaigns
1

Who reported them (2)

Suyang Zhong
9
mrigger
1

Every bug on record (11)

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
2024-09-02 Unexpected results when using string concatenation for INTEGER fixed Suyang Zhong
2024-09-02 Unexpected error and crash after creating a partial index fixed Suyang Zhong
2024-07-02 Unexpected results after creating partial index fixed Suyang Zhong
2024-05-02 Unexpected results when using CASE WHEN with RIGHT JOIN fixed Suyang Zhong
2024-02-21 Unexpected results when using newline in string closed not a bug suyZhong
2023-11-27 Unexpected Results when Using Natural Right Join fixed Suyang Zhong
2023-11-20 Crash potentially caused by BETWEEN Operator fixed Suyang Zhong
2023-11-10 Potential bug in BETWEEN operator fixed mrigger
2023-06-12 Unexpected results when the join condition contains the OR predicate fixed Suyang Zhong
2023-03-12 Unexpected Results when Using CASE-WHEN with LEFT JOIN fixed Suyang Zhong
Unexpected results when using LIKE with boolean values verified Suyang Zhong

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.