gold
SELECT type FROM event WHERE location = 'MU 215'
this statement states no ordering of its own
sha256:a33efd5292c73b98daf777fbe372080cd623331481f45ded14ad3b5b52fce135
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)
Mention the category of events which were held at MU 215.
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 type FROM event WHERE location = 'MU 215'
this statement states no ordering of its own
sha256:a33efd5292c73b98daf777fbe372080cd623331481f45ded14ad3b5b52fce135
from evidence-gold.json, 19 rows
| typeTEXT |
|---|
| Meeting |
| Election |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Election |
| Meeting |
| Meeting |
| Meeting |
| Meeting |
| Guest Speaker |
| Meeting |
| Guest Speaker |
| Meeting |
| Meeting |
| Meeting |
| 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:a33efd5292c73b98daf777fbe372080cd623331481f45ded14ad3b5b52fce135",
"baseline_result": {
"columns": [
{
"name": "type",
"declared_type": "TEXT"
}
],
"row_count": 19,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Election"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Election"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
]
],
"result_hash": "sha256:a33efd5292c73b98daf777fbe372080cd623331481f45ded14ad3b5b52fce135"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:b09e640cedbaeb6714c1d2f99a41db6ac80500dc77086886b613b759c598bbf4",
"result": {
"columns": [
{
"name": "type",
"declared_type": "TEXT"
}
],
"row_count": 19,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Meeting"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Election"
}
],
[
{
"type": "str",
"value": "Guest Speaker"
}
],
[
{
"type": "str",
"value": "Election"
}
],
[
{
"type": "str",
"value": "Meeting"
}
]
],
"result_hash": "sha256:b09e640cedbaeb6714c1d2f99a41db6ac80500dc77086886b613b759c598bbf4"
}
},
"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, 3 rows
| Meeting |
| Guest Speaker |
| Election |
{
"heuristic": true,
"rows": 19,
"distinct_rows": 3,
"repeated_rows": 3,
"largest_repeat": 10,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
10,
7,
2
]
}
SELECT type FROM event WHERE location = 'MU 215'
result_hash sha256:a33efd5292c73b98daf777fbe372080cd623331481f45ded14ad3b5b52fce135 recomputed from this JSON: match
record_hash sha256:74a06e43119ddc6e42381a30ee9a534d58fc3b9490a9f407dc1d0011c95ca3ef recomputed from this JSON: match
from evidence-gold.json, 19 rows
| typeTEXT |
|---|
| Meeting |
| Election |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Guest Speaker |
| Election |
| Meeting |
| Meeting |
| Meeting |
| Meeting |
| Guest Speaker |
| Meeting |
| Guest Speaker |
| Meeting |
| Meeting |
| Meeting |
| 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