gold
SELECT T1.type FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_event WHERE T2.remaining > 30
this statement states no ordering of its own
sha256:ccac66024ed3a58af9d0665e9d91f6a09817ef2f02a5a63546799be9bcd0d394
R-SET GOLD-ONLY duplicate-full-row
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)
List out the type of events which have remaining budget more than 30 USD.
the hint the set supplies: remaining budget more than 30 USD refers to remaining > 30
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.type FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_event WHERE T2.remaining > 30
this statement states no ordering of its own
sha256:ccac66024ed3a58af9d0665e9d91f6a09817ef2f02a5a63546799be9bcd0d394
from evidence-gold.json, 17 rows
| typeTEXT |
|---|
| Guest Speaker |
| Meeting |
| Guest Speaker |
| Meeting |
| Meeting |
| Guest Speaker |
| Guest Speaker |
| Meeting |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Meeting |
| Meeting |
| Meeting |
| Meeting |
| Guest Speaker |
| Meeting |
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:ccac66024ed3a58af9d0665e9d91f6a09817ef2f02a5a63546799be9bcd0d394",
"baseline_result": {
"columns": [
{
"name": "type",
"declared_type": "TEXT"
}
],
"row_count": 17,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
]
],
"result_hash": "sha256:ccac66024ed3a58af9d0665e9d91f6a09817ef2f02a5a63546799be9bcd0d394"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event",
"budget"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:454ef89279e51d4da5dbe327df9c333b5b51d68b26722c6bad92f5891fe4a33b",
"result": {
"columns": [
{
"name": "type",
"declared_type": "TEXT"
}
],
"row_count": 17,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
]
],
"result_hash": "sha256:454ef89279e51d4da5dbe327df9c333b5b51d68b26722c6bad92f5891fe4a33b"
}
},
"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, 2 rows
| Meeting |
| Guest Speaker |
{
"heuristic": true,
"rows": 17,
"distinct_rows": 2,
"repeated_rows": 2,
"largest_repeat": 9,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
9,
8
]
}
SELECT T1.type FROM event AS T1 INNER JOIN budget AS T2 ON T1.event_id = T2.link_to_event WHERE T2.remaining > 30
result_hash sha256:ccac66024ed3a58af9d0665e9d91f6a09817ef2f02a5a63546799be9bcd0d394 recomputed from this JSON: match
record_hash sha256:663e29547e03f6eda3e3047460244308d15757c0294511bc052feabe7d622c89 recomputed from this JSON: match
from evidence-gold.json, 17 rows
| typeTEXT |
|---|
| Guest Speaker |
| Meeting |
| Guest Speaker |
| Meeting |
| Meeting |
| Guest Speaker |
| Guest Speaker |
| Meeting |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Meeting |
| Meeting |
| Meeting |
| Meeting |
| Guest Speaker |
| Meeting |
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-SET