← All database systems

Presto is supported by SQLancer — the main repository ships a testing implementation for it. SQLancer is credited with 4 bugs in it,. Its source is at prestodb/presto.

SQLancer and this project

Adoption proposed, not yet shown

The project's developers have proposed adopting SQLancer without anything yet showing the project running it. An intention is not use, so this counts towards no figure on the impact page.

tdcmeehan, contributor of the Presto project, proposed adopting SQLancer; the issue is open.

using [SQLAncer
Issue in the Presto tracker proposing SQLancer, opened by tdcmeehan (contributor).
prestodb/presto/issues/23324

How the bugs break down

By year reported

Year not recorded
4

Who found them

Reporter not recorded
4

By status

Fixed
1
Open
3

By symptom

Unclassified
4

By technique

Technique not recorded
4

Why each bug counts

Listed in the project's own bug repository
4

Every bug on record (4)

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
— VerifyError: Bad type on operand stack in CASE with mixed numeric types open — —
— Query fail with error `failed: at index 1` fixed — —
— Constant folding fails during case statement with mixed long decimal and integral types open — —
— Compiler failed with complex CASE expression using SOME comparison 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.