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)
What department offers the major that Pierce and Guidi took?
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.department FROM member AS T1 INNER JOIN major AS T2 ON T1.link_to_major = T2.major_id WHERE T1.last_name = 'Pierce' OR T1.last_name = 'Guidi'this statement states no ordering of its own
sha256:053a5f0f398ed039dbd2ca9036dec7043e97da145383ba212cb37505b91f552c
from evidence-gold.json, 2 rows
| departmentTEXT |
|---|
| Civil and Environmental Engineering Department |
| Civil and Environmental Engineering Department |
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:053a5f0f398ed039dbd2ca9036dec7043e97da145383ba212cb37505b91f552c",
"baseline_result": {
"columns": [
{
"name": "department",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Civil and Environmental Engineering Department"
}
],
[
{
"type": "str",
"value": "Civil and Environmental Engineering Department"
}
]
],
"result_hash": "sha256:053a5f0f398ed039dbd2ca9036dec7043e97da145383ba212cb37505b91f552c"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"member",
"major"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:053a5f0f398ed039dbd2ca9036dec7043e97da145383ba212cb37505b91f552c",
"result": {
"columns": [
{
"name": "department",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Civil and Environmental Engineering Department"
}
],
[
{
"type": "str",
"value": "Civil and Environmental Engineering Department"
}
]
],
"result_hash": "sha256:053a5f0f398ed039dbd2ca9036dec7043e97da145383ba212cb37505b91f552c"
}
},
"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
| Civil and Environmental Engineering Department |
{
"heuristic": true,
"rows": 2,
"distinct_rows": 1,
"repeated_rows": 1,
"largest_repeat": 2,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
2
]
}SELECT T2.department FROM member AS T1 INNER JOIN major AS T2 ON T1.link_to_major = T2.major_id WHERE T1.last_name = 'Pierce' OR T1.last_name = 'Guidi'result_hash sha256:053a5f0f398ed039dbd2ca9036dec7043e97da145383ba212cb37505b91f552c recomputed from this JSON: match
record_hash sha256:4a1aace13caebb78e113744740479f95c9e01d9d7e2595836154422aa3348932 recomputed from this JSON: match
from evidence-gold.json, 2 rows
| departmentTEXT |
|---|
| Civil and Environmental Engineering Department |
| Civil and Environmental Engineering Department |
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