R-ORD GOLD-ONLY arbitrary-cut not-a-function-of-the-data
superhero · mini_dev_postgresql from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_postgresql.json
What is the hero's full name with the highest attribute in strength?
the hint the set supplies: highest attribute in strength refers to MAX(attribute_value) WHERE attribute_name = 'strength';
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.full_name FROM superhero AS T1 INNER JOIN hero_attribute AS T2 ON T1.id = T2.hero_id INNER JOIN attribute AS T3 ON T2.attribute_id = T3.id WHERE T3.attribute_name = 'Strength' ORDER BY T2.attribute_value DESC NULLS LAST LIMIT 1sha256:95c4d15ea05cd1284e86bc62aa6252c9aec8079ded2022783dd52aedb34b503b
from evidence-gold.json, 1 row
| full_nametext |
|---|
| Richard Milhouse Jones |
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": "t2.attribute_value",
"column": "hero_attribute.attribute_value",
"declared_type": "bigint",
"not_applicable": "the column is not declared as text"
}
]
}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, 10 rows
| - | 100 |
| - | 100 |
| Abraxas | 100 |
| Robert Bruce Banner | 100 |
| Diana of Themyscira | 100 |
| Heracles | 100 |
| - | 100 |
| Benjamin Kirby Tennyson | 100 |
| - | 100 |
| - | 100 |
{
"heuristic": true,
"cut": 1,
"offset": 0,
"distinct_kept": false,
"unbounded_sql": "SELECT t1.full_name, t2.attribute_value AS attestql_ordering_key_0 FROM superhero t1 JOIN hero_attribute t2 ON t1.id = t2.hero_id JOIN attribute t3 ON t2.attribute_id = t3.id WHERE t3.attribute_name = 'Strength' ORDER BY t2.attribute_value DESC NULLS LAST",
"unbounded_rows": 623,
"projected_columns": [
"full_name"
],
"ordering_key_columns": [
"attestql_ordering_key_0"
],
"ordering_keys": [
{
"key": "t2.attribute_value",
"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,
2,
3,
4,
5,
6,
7,
8,
9
],
"tied_rows": 63,
"distinct_projected_answers": 36,
"rows": [
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "Abraxas"
}
],
[
{
"type": "str",
"value": "Robert Bruce Banner"
}
],
[
{
"type": "str",
"value": "Diana of Themyscira"
}
],
[
{
"type": "str",
"value": "Heracles"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "Benjamin Kirby Tennyson"
}
],
[
{
"type": "str",
"value": "-"
}
],
[
{
"type": "str",
"value": "-"
}
]
]
},
"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
from smells.json, 1 row
| - |
{
"heuristic": true,
"rule": "R-ORD",
"baseline_result_hash": "sha256:95c4d15ea05cd1284e86bc62aa6252c9aec8079ded2022783dd52aedb34b503b",
"baseline_result": {
"columns": [
{
"name": "full_name",
"declared_type": "text"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "Richard Milhouse Jones"
}
]
],
"result_hash": "sha256:95c4d15ea05cd1284e86bc62aa6252c9aec8079ded2022783dd52aedb34b503b"
},
"planner_statistics": {
"attribute": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 6
},
"superhero": {
"last_analyze": null,
"last_autoanalyze": "2026-09-08 05:19:12.518866+00",
"n_mod_since_analyze": 0
},
"hero_attribute": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 3738
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"attribute",
"superhero",
"hero_attribute"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"laptimes": 400524,
"legalities": 427907,
"posthistory": 303155,
"trans": 1056320,
"yearmonth": 383282
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "not_equal",
"differs": true,
"result_hash": "sha256:7b3cda881dc045afd273609e8f96ef79019d7ba4fe6308648b9fffc5612c7c29",
"result": {
"columns": [
{
"name": "full_name",
"declared_type": "text"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "-"
}
]
],
"result_hash": "sha256:7b3cda881dc045afd273609e8f96ef79019d7ba4fe6308648b9fffc5612c7c29"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT T1.full_name FROM superhero AS T1 INNER JOIN hero_attribute AS T2 ON T1.id = T2.hero_id INNER JOIN attribute AS T3 ON T2.attribute_id = T3.id WHERE T3.attribute_name = 'Strength' ORDER BY T2.attribute_value DESC NULLS LAST LIMIT 1result_hash sha256:95c4d15ea05cd1284e86bc62aa6252c9aec8079ded2022783dd52aedb34b503b recomputed from this JSON: match
record_hash sha256:296ebf0b954f33bc4b9363ebccb44f2d0e381ab3ce828192e5e8e4342b9647aa recomputed from this JSON: match
from evidence-gold.json, 1 row
| full_nametext |
|---|
| Richard Milhouse Jones |
re-run this statement read-only against PostgreSQL 16.15 (Debian 16.15-1.pgdg13+2) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit | server=172.17.0.2/32:5432 | database=bird under the session settings and over the data this record's fixture digest names, and compare the two results under R-ORD