Detecting Logical Bugs in DBMS via Isomerism Fuzz System
Read the paper · doi:10.1109/iaecst64597.2024.11117732
What this paper does with SQLancer
How it was classified
uses infrastructure — yes (implementation)
M1 states the system was implemented within SQLancer, and M4 that the query generation draws on SQLancer's design principles with certain modifications. M1's characters are separated by spaces in the PDF's text layer, which is damage to the rendering rather than to the words.
The query generation approach draws on the design principles of SQLancer [16], with certain modifications.
extends technique — no
No technique is extended; the citation is background.
compares with — no
No empirical comparison against SQLancer is reported in the mentions.
describes as state of the art — no
The citation does not characterise SQLancer as the state of the art.
SQLancer publications it cites (3)
Bibliography entries that resolved to a SQLancer publication, or to a paper by one of the project's authors. A sentence citing one of these numbers is a reference to SQLancer even when it never writes the name.
| # | Entry | Matched as |
|---|---|---|
| 13 | Rigger, M., Su, Z. (2020) Detecting Optimization Bugs in Database Engines via Non-Optimizing Reference Engine Construction. In: Proceedings of the ACM Joint Meeting on European Software Engineering Conference and Symp... | sqlancer publication · NOREC |
| 14 | Rigger, M., Su, Z. (2020) Finding Bugs in Database Systems via Query Partitioning. Proceedings of the ACM on Programming Languages, 4(OOPSLA): 1–30. | sqlancer publication · TLP |
| 16 | Rigger, M., Su, Z. (2020) Testing Database Management Systems via Pivoted Query Synthesis. In: Proceedings of the 41st ACMSIGPLAN Conference on Programming Language Design and Implementation (PLDI). London. pp. 733–74... | sqlancer publication |
Every place it refers to SQLancer (6)
6 sentences, each stored verbatim from the extracted text with where it was found and how. “Citation marker” means the sentence names no tool at all and was reached through a reference number that resolved to a SQLancer publication.
| Id | Sentence | Found by | Where |
|---|---|---|---|
| M1 | The paper sets this passage with letter-spacing, which extraction cannot undo — the sentence is there, but no readable form of it is. |
name |
page 1 |
| M2 | [13] proposed the Non-Optimized Reference Engine Construction (NoREC), aimed at detecting optimization bugs in DBMSs by comparing optimized and non-optimized query s. |
technique |
page 2 |
| M3 | [14] they proposed a query partitioning differential detection method. |
technique |
page 2 |
| M4 | The query generation approach draws on the design principles of SQLancer [16], with certain modifications. |
name |
page 3 |
| M5 | In addition, SQLancer supports not only basic query generation but also more advanced nested queries (such as subqueries) and union queries (such as UNION). |
name |
page 3 |
| M6 | CONCLUSION This paper proposes a novel fuzz system for DBMS, offering a new perspective and approach for differential testing, and implements the system in SQLancer. |
name |
page 5 |