R-SET GOLD-ONLY duplicate-full-row
debit_card_specializing · dev_20251106-00000-of-00001 from https://huggingface.co/datasets/birdsql/bird_sql_dev_20251106/resolve/3c11fb193e5439b338e23677fa0aae11e8b85db9/data/dev_20251106-00000-of-00001.json (commit 3c11fb19, downloaded 2026-09-07)
For the deal happened at 2012/8/24 12:42:00, which country was it?
the hint the set supplies: '2012/8/24 12:42:00' can refer to date = '2012-08-24' AND T1.time = '12:42:00' in the database
This question was audited without a prediction beside it, so there is nothing to compare the gold with. The probes below read the gold alone.
SELECT T2.Country FROM transactions_1k AS T1 INNER JOIN gasstations AS T2 ON T1.GasStationID = T2.GasStationID WHERE T1.Date = '2012-08-24' AND T1.Time = '12:42:00'this statement states no ordering of its own
sha256:5c5d70c20a5227bdb300602e3d57167f7995c47f58c447f939d3a8e601c2a87a
from evidence-gold.json, 2 rows
| CountryTEXT |
|---|
| CZE |
| CZE |
A smell is a mechanical reason to read this gold statement again. It is a heuristic: it does not state that the statement is wrong, and a maintainer decides.
this statement orders by a text column holding only numbers, and ordering it as a number gives a different answer, so the gold may be sorting 9.5 above 10
the statement states no top level ORDER BY
{
"heuristic": true,
"reason": "the statement states no top level ORDER BY"
}this statement cuts its result at a LIMIT that does not decide which rows come back, so a different but equally correct statement can return other rows and score zero
the statement states no LIMIT
{
"heuristic": true,
"reason": "the statement states no LIMIT"
}rerun over the same rows in another physical order this statement gives another answer, so its result depends on how the rows are stored and not only on the data
{
"heuristic": true,
"rule": "R-SET",
"baseline_result_hash": "sha256:5c5d70c20a5227bdb300602e3d57167f7995c47f58c447f939d3a8e601c2a87a",
"baseline_result": {
"columns": [
{
"name": "Country",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "CZE"
}
],
[
{
"type": "str",
"value": "CZE"
}
]
],
"result_hash": "sha256:5c5d70c20a5227bdb300602e3d57167f7995c47f58c447f939d3a8e601c2a87a"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"transactions_1k",
"gasstations"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"yearmonth": 383282
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:5c5d70c20a5227bdb300602e3d57167f7995c47f58c447f939d3a8e601c2a87a",
"result": {
"columns": [
{
"name": "Country",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "CZE"
}
],
[
{
"type": "str",
"value": "CZE"
}
]
],
"result_hash": "sha256:5c5d70c20a5227bdb300602e3d57167f7995c47f58c447f939d3a8e601c2a87a"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}this statement returns the same whole row more than once and never says DISTINCT, so a statement answering the same question once per row disagrees on multiplicity alone
from smells.json, 1 row
| CZE |
{
"heuristic": true,
"rows": 2,
"distinct_rows": 1,
"repeated_rows": 1,
"largest_repeat": 2,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
2
]
}SELECT T2.Country FROM transactions_1k AS T1 INNER JOIN gasstations AS T2 ON T1.GasStationID = T2.GasStationID WHERE T1.Date = '2012-08-24' AND T1.Time = '12:42:00'result_hash sha256:5c5d70c20a5227bdb300602e3d57167f7995c47f58c447f939d3a8e601c2a87a recomputed from this JSON: match
record_hash sha256:33764f07ddda5d565aa92105f70caf03932afc1d8c95983ef856dc3c60e1c0e6 recomputed from this JSON: match
from evidence-gold.json, 2 rows
| CountryTEXT |
|---|
| CZE |
| CZE |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/debit_card_specializing/debit_card_specializing.sqlite | size=34635776 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET