R-SET NOT_EQUAL
student_club · 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
List the names of closed event as "game" that was closed from 3/15/2019 to 3/20/2020.
the hint the set supplies: name of events refers event_name; game event that was closed refers to type = 'Game' where status = 'Closed'; event_date BETWEEN '2019-03-15' and '2020-03-20';
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 names, 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 event_name FROM event WHERE type = 'Game' AND DATE(SUBSTR(event_date, 1, 10)) BETWEEN '2019-03-15' AND '2020-03-20' AND status = 'Closed'this statement states no ordering of its own
sha256:e696aae1a5333b7b93b45035a666b54566afe4c048b471d3009f14cfad491010
SELECT event_name
FROM event
WHERE type = 'Game' AND status = 'Closed' AND event_date BETWEEN '2019-03-15' AND '2020-03-20'this statement states no ordering of its own
sha256:83fa9be53364a45d11c7cb4af328b1cfbe56737a22f5b6846e22846f5886d7f3
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 | event_nametext |
|---|---|
| no rows |
from counterexample.json, 1 row, up to 25 shown per side
| side | event_nametext |
|---|---|
| second | Football game |
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
| event_nametext |
|---|
| Football game |
| Women's Soccer |
from counterexample.json, 3 rows
| event_nametext |
|---|
| Women's Soccer |
| Football game |
| Football game |
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:e696aae1a5333b7b93b45035a666b54566afe4c048b471d3009f14cfad491010",
"baseline_result": {
"columns": [
{
"name": "event_name",
"declared_type": "text"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Football game"
}
],
[
{
"type": "str",
"value": "Women's Soccer"
}
]
],
"result_hash": "sha256:e696aae1a5333b7b93b45035a666b54566afe4c048b471d3009f14cfad491010"
},
"planner_statistics": {
"event": {
"last_analyze": null,
"last_autoanalyze": null,
"n_mod_since_analyze": 42
}
},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event"
],
"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:e696aae1a5333b7b93b45035a666b54566afe4c048b471d3009f14cfad491010",
"result": {
"columns": [
{
"name": "event_name",
"declared_type": "text"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Football game"
}
],
[
{
"type": "str",
"value": "Women's Soccer"
}
]
],
"result_hash": "sha256:e696aae1a5333b7b93b45035a666b54566afe4c048b471d3009f14cfad491010"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT DISTINCT event_name FROM event WHERE type = 'Game' AND DATE(SUBSTR(event_date, 1, 10)) BETWEEN '2019-03-15' AND '2020-03-20' AND status = 'Closed'result_hash sha256:e696aae1a5333b7b93b45035a666b54566afe4c048b471d3009f14cfad491010 recomputed from this JSON: match
record_hash sha256:e933cf865032f2cd6d7992187add3657bd3b3d56e9e4f9eeb8627fe8f35a1452 recomputed from this JSON: match
from evidence-gold.json, 2 rows
| event_nametext |
|---|
| Football game |
| Women's Soccer |
SELECT event_name
FROM event
WHERE type = 'Game' AND status = 'Closed' AND event_date BETWEEN '2019-03-15' AND '2020-03-20'result_hash sha256:83fa9be53364a45d11c7cb4af328b1cfbe56737a22f5b6846e22846f5886d7f3 recomputed from this JSON: match
record_hash sha256:e61de3d71bcac2fd1117534ea3af01e9af0ee794123f984fcb458376b3c23b4c recomputed from this JSON: match
from evidence-second.json, 3 rows
| event_nametext |
|---|
| Women's Soccer |
| Football game |
| Football game |
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