Technical Perspective DIAMetrics
Read the paper · doi:10.1145/3471485.3471491
What this paper does with SQLancer
How it was classified
uses infrastructure — no
SQLancer is cited as related work; no reuse of its code, generator or workload is described.
extends technique — no
No SQLancer technique is extended; the citation is background.
compares with — no
No empirical comparison against SQLancer or one of its oracles is reported.
describes as state of the art — no
The text does not describe SQLancer as the state of the art.
What could not be determined
- Whether the perspective says anything about SQLancer in prose. The single mention is a reference-list entry, so the extracted text offers nothing to judge from.
SQLancer publications it cites (1)
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 |
|---|---|---|
| 4 | M. Rigger and Z. Su. Finding bugs in database systems via query partitioning. In OOPSLA. ACM, 2020. | sqlancer publication · TLP |
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 | It inspired me to think about novel directions, possibly taking automatic benchmark extraction from performance monitoring accountability also towards correctness testing: one could envision enriching workload summarization with new dimensions such as code coverage [5] and automatic generation of query correctness o... |
citation marker |
page 1 |