R-SET GOLD-ONLY duplicate-full-row
codebase_community · 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 list the users' display names whose posts had over 20000 views in 2011.
the hint the set supplies: had over 20000 views in 2011 refers to ViewCount > 20000 where YEAR(CreationDate) = 2011;
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.DisplayName FROM users AS T1 INNER JOIN posts AS T2 ON T1.Id = T2.OwnerUserId WHERE STRFTIME('%Y', T2.CreaionDate) = '2011' AND T2.ViewCount > 20000this statement states no ordering of its own
sha256:8a63461606889c3eabec14bb655c9e5a1f412b398f29aa20b1727c73f8499861
from evidence-gold.json, 24 rows
| DisplayNameTEXT |
|---|
| Alex |
| Yahel |
| Jana |
| Omar Kooheji |
| Yuriy Petrovskiy |
| MYaseen208 |
| even |
| Jeromy Anglim |
| Chris |
| BEF |
| Han Lin Shang |
| JanD |
| Legend |
| Sue |
| Tal Galili |
| Short Elizabeth |
| Dbr |
| paul |
| Tim |
| JackOfAll |
| PhD |
| pmgjones |
| PhD |
| xiaohan2012 |
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:8a63461606889c3eabec14bb655c9e5a1f412b398f29aa20b1727c73f8499861",
"baseline_result": {
"columns": [
{
"name": "DisplayName",
"declared_type": "TEXT"
}
],
"row_count": 24,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "Alex"
}
],
[
{
"type": "str",
"value": "Yahel"
}
],
[
{
"type": "str",
"value": "Jana"
}
],
[
{
"type": "str",
"value": "Omar Kooheji"
}
],
[
{
"type": "str",
"value": "Yuriy Petrovskiy"
}
],
[
{
"type": "str",
"value": "MYaseen208"
}
],
[
{
"type": "str",
"value": "even"
}
],
[
{
"type": "str",
"value": "Jeromy Anglim"
}
],
[
{
"type": "str",
"value": "Chris"
}
],
[
{
"type": "str",
"value": "BEF"
}
]
],
"result_hash": "sha256:8a63461606889c3eabec14bb655c9e5a1f412b398f29aa20b1727c73f8499861"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"users",
"posts"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"postHistory": 303155
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:cc7500b3a2a9321c1f1b2c657eb6b18a815db465a62bace1525ffe6d6322848a",
"result": {
"columns": [
{
"name": "DisplayName",
"declared_type": "TEXT"
}
],
"row_count": 24,
"truncated": false,
"rows_shown": 10,
"rows": [
[
{
"type": "str",
"value": "paul"
}
],
[
{
"type": "str",
"value": "Legend"
}
],
[
{
"type": "str",
"value": "JackOfAll"
}
],
[
{
"type": "str",
"value": "Omar Kooheji"
}
],
[
{
"type": "str",
"value": "even"
}
],
[
{
"type": "str",
"value": "PhD"
}
],
[
{
"type": "str",
"value": "Short Elizabeth"
}
],
[
{
"type": "str",
"value": "Jeromy Anglim"
}
],
[
{
"type": "str",
"value": "MYaseen208"
}
],
[
{
"type": "str",
"value": "Tim"
}
]
],
"result_hash": "sha256:cc7500b3a2a9321c1f1b2c657eb6b18a815db465a62bace1525ffe6d6322848a"
}
},
"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
| PhD |
{
"heuristic": true,
"rows": 24,
"distinct_rows": 23,
"repeated_rows": 1,
"largest_repeat": 2,
"result_bounded": false,
"distinct_stated": false,
"set_operation": false,
"repeats_of_the_rows_shown": [
2
]
}SELECT T1.DisplayName FROM users AS T1 INNER JOIN posts AS T2 ON T1.Id = T2.OwnerUserId WHERE STRFTIME('%Y', T2.CreaionDate) = '2011' AND T2.ViewCount > 20000result_hash sha256:8a63461606889c3eabec14bb655c9e5a1f412b398f29aa20b1727c73f8499861 recomputed from this JSON: match
record_hash sha256:c938973c67753968578cbc3373c64adbf9c911e6d815c0346fdc07fbc3cb915a recomputed from this JSON: match
from evidence-gold.json, 24 rows
| DisplayNameTEXT |
|---|
| Alex |
| Yahel |
| Jana |
| Omar Kooheji |
| Yuriy Petrovskiy |
| MYaseen208 |
| even |
| Jeromy Anglim |
| Chris |
| BEF |
| Han Lin Shang |
| JanD |
| Legend |
| Sue |
| Tal Galili |
| Short Elizabeth |
| Dbr |
| paul |
| Tim |
| JackOfAll |
| PhD |
| pmgjones |
| PhD |
| xiaohan2012 |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/dev/dev_databases/codebase_community/codebase_community.sqlite | size=481419264 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET