R-ORD GOLD-ONLY arbitrary-cut
student_club · 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)
What is the event that has the highest attendance of the students from the Student_Club?
the hint the set supplies: highest attendance refers to the event with the most attendees
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 T1.event_name FROM event AS T1 INNER JOIN attendance AS T2 ON T1.event_id = T2.link_to_event GROUP BY T1.event_name ORDER BY COUNT(T2.link_to_event) DESC LIMIT 1sha256:ebfc3fa5d6d12ba09adba1a3dad8c15e79e799850304ca68d94a3dcb4996f659
from evidence-gold.json, 1 row
| event_nameTEXT |
|---|
| Yearly Kickoff |
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
no ORDER BY key resolves to a text column
{
"heuristic": true,
"reason": "no ORDER BY key resolves to a text column",
"keys": [
{
"key": "COUNT(T2.link_to_event)",
"not_applicable": "the key is an expression and not a column"
}
]
}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, 2 rows
| Yearly Kickoff | 30 |
| Registration | 30 |
{
"heuristic": true,
"cut": 1,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT T1.event_name, COUNT(T2.link_to_event) AS attestql_ordering_key_0 FROM event AS T1 INNER JOIN attendance AS T2 ON T1.event_id = T2.link_to_event GROUP BY T1.event_name ORDER BY COUNT(T2.link_to_event) DESC",
"unbounded_rows": 16,
"projected_columns": [
"event_name"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "COUNT(T2.link_to_event)",
"direction": "desc",
"nulls": "last",
"nulls_first_in_effect": false,
"returned_rows_null_in_this_key": 0,
"fires": false
}
],
"tied_at_the_cut": {
"positions": [
0,
1
],
"tied_rows": 2,
"distinct_projected_answers": 2,
"rows": [
[
{
"type": "str",
"value": "Yearly Kickoff"
}
],
[
{
"type": "str",
"value": "Registration"
}
]
]
},
"case": "tie-at-the-cut"
}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-ORD",
"baseline_result_hash": "sha256:ebfc3fa5d6d12ba09adba1a3dad8c15e79e799850304ca68d94a3dcb4996f659",
"baseline_result": {
"columns": [
{
"name": "event_name",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Yearly Kickoff"
}
]
],
"result_hash": "sha256:ebfc3fa5d6d12ba09adba1a3dad8c15e79e799850304ca68d94a3dcb4996f659"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event",
"attendance"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:ebfc3fa5d6d12ba09adba1a3dad8c15e79e799850304ca68d94a3dcb4996f659",
"result": {
"columns": [
{
"name": "event_name",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Yearly Kickoff"
}
]
],
"result_hash": "sha256:ebfc3fa5d6d12ba09adba1a3dad8c15e79e799850304ca68d94a3dcb4996f659"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT T1.event_name FROM event AS T1 INNER JOIN attendance AS T2 ON T1.event_id = T2.link_to_event GROUP BY T1.event_name ORDER BY COUNT(T2.link_to_event) DESC LIMIT 1result_hash sha256:ebfc3fa5d6d12ba09adba1a3dad8c15e79e799850304ca68d94a3dcb4996f659 recomputed from this JSON: match
record_hash sha256:3a6e92dc03810fa510acbe4e82c57d9950b5545ba09810ae9ea3f68d5b436d5b recomputed from this JSON: match
from evidence-gold.json, 1 row
| event_nameTEXT |
|---|
| Yearly Kickoff |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/student_club/student_club.sqlite | size=2641920 under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD