R-SET GOLD-ONLY arbitrary-cut not-a-function-of-the-data
european_football_2 · 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)
Please state the finishing rate and curve score of the player who has the heaviest weight.
the hint the set supplies: finishing rate refer to finishing; curve score refer to curve; heaviest weight refers to MAX(weight)
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.
read by hand, 2026-09-07: wrong the gold does not answer its question on this data
two players share the largest weight, and the one the subquery picks has 14 attribute rows carrying three different (finishing, curve) pairs, which the outer LIMIT 1 cuts without an ordering
a maintainer's reading of this question, out of classification.json, copied from plans/reports/bird-dev-sqlite-260907/classification.json. It is not a verdict and nothing above it was computed from it.
SELECT id, finishing, curve FROM Player_Attributes WHERE player_api_id = ( SELECT player_api_id FROM Player ORDER BY weight DESC LIMIT 1 ) LIMIT 1this statement states no ordering of its own
sha256:7be3a3e124221b7a732412791def7b6068c7f564d65e79f00c30d9416d36261a
from evidence-gold.json, 1 row
| idINTEGER | finishingINTEGER | curveINTEGER |
|---|---|---|
| 98022 | 13 | 13 |
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
from smells.json, 1 row
| 98024 | 13 | 13 |
{
"heuristic": true,
"case": "no-ordering",
"cut": 1,
"why": "the statement bounds its result and states no ORDER BY, so which rows it returns is whichever ones the plan produced first",
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"Player_Attributes",
"Player"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"verdict": "not_equal",
"gold_result": {
"columns": [
{
"name": "id",
"declared_type": "INTEGER"
},
{
"name": "finishing",
"declared_type": "INTEGER"
},
{
"name": "curve",
"declared_type": "INTEGER"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "int",
"value": 98022
},
{
"type": "int",
"value": 13
},
{
"type": "int",
"value": 13
}
]
],
"result_hash": "sha256:7be3a3e124221b7a732412791def7b6068c7f564d65e79f00c30d9416d36261a"
},
"shuffled_result": {
"columns": [
{
"name": "id",
"declared_type": "INTEGER"
},
{
"name": "finishing",
"declared_type": "INTEGER"
},
{
"name": "curve",
"declared_type": "INTEGER"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "int",
"value": 98024
},
{
"type": "int",
"value": 13
},
{
"type": "int",
"value": 13
}
]
],
"result_hash": "sha256:f53fd7531e023cd937cc84f368e076980b07abb8e2fe3474a7464e7f3e1338e8"
}
}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
from smells.json, 1 row
| 98024 | 13 | 13 |
{
"heuristic": true,
"rule": "R-SET",
"baseline_result_hash": "sha256:7be3a3e124221b7a732412791def7b6068c7f564d65e79f00c30d9416d36261a",
"baseline_result": {
"columns": [
{
"name": "id",
"declared_type": "INTEGER"
},
{
"name": "finishing",
"declared_type": "INTEGER"
},
{
"name": "curve",
"declared_type": "INTEGER"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "int",
"value": 98022
},
{
"type": "int",
"value": 13
},
{
"type": "int",
"value": 13
}
]
],
"result_hash": "sha256:7be3a3e124221b7a732412791def7b6068c7f564d65e79f00c30d9416d36261a"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"Player_Attributes",
"Player"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "not_equal",
"differs": true,
"result_hash": "sha256:f53fd7531e023cd937cc84f368e076980b07abb8e2fe3474a7464e7f3e1338e8",
"result": {
"columns": [
{
"name": "id",
"declared_type": "INTEGER"
},
{
"name": "finishing",
"declared_type": "INTEGER"
},
{
"name": "curve",
"declared_type": "INTEGER"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "int",
"value": 98024
},
{
"type": "int",
"value": 13
},
{
"type": "int",
"value": 13
}
]
],
"result_hash": "sha256:f53fd7531e023cd937cc84f368e076980b07abb8e2fe3474a7464e7f3e1338e8"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT id, finishing, curve FROM Player_Attributes WHERE player_api_id = ( SELECT player_api_id FROM Player ORDER BY weight DESC LIMIT 1 ) LIMIT 1result_hash sha256:7be3a3e124221b7a732412791def7b6068c7f564d65e79f00c30d9416d36261a recomputed from this JSON: match
record_hash sha256:49cc3fee09c36af273702c8b32c7ef9ea21d69a831e145ce4a8301162a774371 recomputed from this JSON: match
from evidence-gold.json, 1 row
| idINTEGER | finishingINTEGER | curveINTEGER |
|---|---|---|
| 98022 | 13 | 13 |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/european_football_2/european_football_2.sqlite | size=597754880 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET