Agentic Proof and Property-Based Testing via Property-Templates in Data-Intensive Computing
Read the paper · arXiv:2607.09072
What this paper does with SQLancer
How it was classified
uses infrastructure — no
SQLancer is cited, not used; nothing in the mentions describes reusing its code.
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 (2)
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 |
|---|---|---|
| 28 | M. Rigger and Z. Su, “Finding Bugs in Database Systems via Query Partitioning,”Proceedings of the ACM on Programming Languages, vol. 4, no. OOPSLA, pp. 1–30, 2020. | sqlancer publication · TLP |
| 29 | ——, “Detecting Optimization Bugs in Database Engines via NonOptimizing Reference Engine Construction,” inProceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Found... | sqlancer publication · NOREC |
Every place it refers to SQLancer (1)
1 sentence, 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 | On the testing side, SQLancer detects logic and optimization bugs in database engines through constructed oracles such as query partitioning and a non-optimizing reference engine [ 28], [29]. |
name |
C Cross-Validation: PBT Against Formal Proofs page 10 |