R-SET NOT_EQUAL
debit_card_specializing · 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
Please list the disparate time of the transactions taken place in the gas stations from chain no. 11.
NOT_EQUAL states that these two statements disagree on this data under this rule. It does not state which of them is wrong.
read by hand, 2026-09-04: B harmless: one distinct row repeated; DISTINCT added by the prediction; a list under twice the answer with every row present
2 distinct times, 3 rows
a maintainer's reading of this question, out of classification.json, copied from plans/reports/prediction-mode-260904-real-predictions/classification.json. It is not a verdict and nothing above it was computed from it.
SELECT DISTINCT T1.Time FROM transactions_1k AS T1 INNER JOIN gasstations AS T2 ON T1.GasStationID = T2.GasStationID WHERE T2.ChainID = 11this statement states no ordering of its own
sha256:4701baecc28e772c46bb3ad1b6f3040880202d59758e9ca492f474c149cc58a7
SELECT transactions_1k.time
FROM transactions_1k
JOIN gasstations ON transactions_1k.gasstationid = gasstations.gasstationid
WHERE gasstations.chainid = 11this statement states no ordering of its own
sha256:53012c355a0063a69d9140f9884d79c78f2258edc1e0bf9d2df61c3fecef0e99
The marked tokens are where the two texts differ. Two statements that differ everywhere can return the same rows, and two that differ in one token can return other rows; the verdict above is read off the results.
from counterexample.json, 0 rows, up to 25 shown per side
| side | timetext |
|---|---|
| no rows |
from counterexample.json, 1 row, up to 25 shown per side
| side | timetext |
|---|---|
| second | 14:29:00 |
set(second_rows) == set(gold_rows), float4/float8 cells as Python float as psycopg2 returns them, numeric as Decimal
https://github.com/bird-bench/mini_dev/blob/main/evaluation/evaluation_ex.py
result_eq: equal row counts and equal column counts, each row unordered as a quick rejection, then the two equal as a list when the gold text holds ORDER BY and as a multiset otherwise, under some permutation of the columns; DISTINCT is not stripped and re-executed, and the cells are PostgreSQL's as psycopg2 returns them
ruiqi-zhong/test-suite-sql-eval, exec_eval.py, result_eq, at commit 48cb78ec: https://github.com/ruiqi-zhong/test-suite-sql-eval/blob/48cb78ecf7f610620206283846c76751b18a1326/exec_eval.py
The class states what makes these two results unequal under this rule, read off the two results and nothing else. It does not state which of the two statements is wrong.
from counterexample.json, 2 rows
| timetext |
|---|
| 11:55:00 |
| 14:29:00 |
from counterexample.json, 3 rows
| timetext |
|---|
| 14:29:00 |
| 14:29:00 |
| 11:55:00 |
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:4701baecc28e772c46bb3ad1b6f3040880202d59758e9ca492f474c149cc58a7",
"baseline_result": {
"columns": [
{
"name": "time",
"declared_type": "text"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "11:55:00"
}
],
[
{
"type": "str",
"value": "14:29:00"
}
]
],
"result_hash": "sha256:4701baecc28e772c46bb3ad1b6f3040880202d59758e9ca492f474c149cc58a7"
},
"planner_statistics": {
"transactions_1k": {
"last_analyze": null,
"last_autoanalyze": "2026-09-08 05:19:51.57727+00",
"n_mod_since_analyze": 0
},
"gasstations": {
"last_analyze": null,
"last_autoanalyze": "2026-09-08 05:19:24.38603+00",
"n_mod_since_analyze": 0
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"transactions_1k",
"gasstations"
],
"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": "equal",
"differs": false,
"result_hash": "sha256:5be1ce19cde3e0d8967c3d06ab72aa07cd4f37b0b35768c7c6932260b3066ebc",
"result": {
"columns": [
{
"name": "time",
"declared_type": "text"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "14:29:00"
}
],
[
{
"type": "str",
"value": "11:55:00"
}
]
],
"result_hash": "sha256:5be1ce19cde3e0d8967c3d06ab72aa07cd4f37b0b35768c7c6932260b3066ebc"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT DISTINCT T1.Time FROM transactions_1k AS T1 INNER JOIN gasstations AS T2 ON T1.GasStationID = T2.GasStationID WHERE T2.ChainID = 11result_hash sha256:4701baecc28e772c46bb3ad1b6f3040880202d59758e9ca492f474c149cc58a7 recomputed from this JSON: match
record_hash sha256:8a95873ac5dc25f25040f25e4506b14674947f676fc25a9a7b134cc5a3e7bd7c recomputed from this JSON: match
from evidence-gold.json, 2 rows
| timetext |
|---|
| 11:55:00 |
| 14:29:00 |
SELECT transactions_1k.time
FROM transactions_1k
JOIN gasstations ON transactions_1k.gasstationid = gasstations.gasstationid
WHERE gasstations.chainid = 11result_hash sha256:53012c355a0063a69d9140f9884d79c78f2258edc1e0bf9d2df61c3fecef0e99 recomputed from this JSON: match
record_hash sha256:b98ec06798a19907bbdda7734e94bf554092d36463d412274b14a6c24419b4e1 recomputed from this JSON: match
from evidence-second.json, 3 rows
| timetext |
|---|
| 14:29:00 |
| 14:29:00 |
| 11:55:00 |
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-SET
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-SET