gold
SELECT T2.date FROM cards AS T1 INNER JOIN rulings AS T2 ON T2.uuid = T1.uuid WHERE T1.name = 'Reminisce'
this statement states no ordering of its own
sha256:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0
R-SET GOLD-ONLY duplicate-full-row
card_games · 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)
When was the ruling for the card 'Reminisce' created?
the hint the set supplies: Reminisce refers to name = 'Reminisce'; when created is the date
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.date FROM cards AS T1 INNER JOIN rulings AS T2 ON T2.uuid = T1.uuid WHERE T1.name = 'Reminisce'
this statement states no ordering of its own
sha256:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0
from evidence-gold.json, 4 rows
| dateTEXT |
|---|
| 2013-07-01 |
| 2013-07-01 |
| 2013-07-01 |
| 2013-07-01 |
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:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0",
"baseline_result": {
"columns": [
{
"name": "date",
"declared_type": "TEXT"
}
],
"row_count": 4,
"truncated": false,
"rows_shown": 4,
"rows": [
[
{
"type": "str",
"value": "2013-07-01"
}
],
[
{
"type": "str",
"value": "2013-07-01"
}
],
[
{
"type": "str",
"value": "2013-07-01"
}
],
[
{
"type": "str",
"value": "2013-07-01"
}
]
],
"result_hash": "sha256:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"cards",
"rulings"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"legalities": 427907
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0",
"result": {
"columns": [
{
"name": "date",
"declared_type": "TEXT"
}
],
"row_count": 4,
"truncated": false,
"rows_shown": 4,
"rows": [
[
{
"type": "str",
"value": "2013-07-01"
}
],
[
{
"type": "str",
"value": "2013-07-01"
}
],
[
{
"type": "str",
"value": "2013-07-01"
}
],
[
{
"type": "str",
"value": "2013-07-01"
}
]
],
"result_hash": "sha256:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0"
}
},
"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
| 2013-07-01 |
{
"heuristic": true,
"rows": 4,
"distinct_rows": 1,
"repeated_rows": 1,
"largest_repeat": 4,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
4
]
}
SELECT T2.date FROM cards AS T1 INNER JOIN rulings AS T2 ON T2.uuid = T1.uuid WHERE T1.name = 'Reminisce'
result_hash sha256:916fb832658305ab2ef50e2a0347acd4b181c8cbadcacd9b5ffe3c552aa2c8b0 recomputed from this JSON: match
record_hash sha256:b1359bc4056f7c78e42f8d28504fae6075f666e50185d5b91c83dd2692632735 recomputed from this JSON: match
from evidence-gold.json, 4 rows
| dateTEXT |
|---|
| 2013-07-01 |
| 2013-07-01 |
| 2013-07-01 |
| 2013-07-01 |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/card_games/card_games.sqlite | size=261820416 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET