R-SET NOT_EQUAL
student_club · mini_dev_sqlite from https://bird-bench.oss-cn-beijing.aliyuncs.com/minidev.zip (sha256 cc48ba16838204e4e214512030cb572eeb5f7bcdd999bae4b9b6ff12ec13b92f, downloaded 2026-09-07), member minidev/MINIDEV/mini_dev_sqlite.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.
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:af87d8f5c8cc016b49fc2102e5d0b351e8cbee1606207ff8444fa26e3157c25b
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:d600a85ebd7554e448ea060e2e2e20ec247fb1ec328a56c3d0cec33b46a0e8d6
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), REAL cells as Python float as sqlite3 returns them, so Python equality holds 1 == 1.0 == True as the benchmark's own scorer does
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 SQLite's as sqlite3 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 |
|---|
| Women's Soccer |
| Football game |
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:af87d8f5c8cc016b49fc2102e5d0b351e8cbee1606207ff8444fa26e3157c25b",
"baseline_result": {
"columns": [
{
"name": "event_name",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Women's Soccer"
}
],
[
{
"type": "str",
"value": "Football game"
}
]
],
"result_hash": "sha256:af87d8f5c8cc016b49fc2102e5d0b351e8cbee1606207ff8444fa26e3157c25b"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"event"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:af87d8f5c8cc016b49fc2102e5d0b351e8cbee1606207ff8444fa26e3157c25b",
"result": {
"columns": [
{
"name": "event_name",
"declared_type": "TEXT"
}
],
"row_count": 2,
"truncated": false,
"rows_shown": 2,
"rows": [
[
{
"type": "str",
"value": "Women's Soccer"
}
],
[
{
"type": "str",
"value": "Football game"
}
]
],
"result_hash": "sha256:af87d8f5c8cc016b49fc2102e5d0b351e8cbee1606207ff8444fa26e3157c25b"
}
},
"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:af87d8f5c8cc016b49fc2102e5d0b351e8cbee1606207ff8444fa26e3157c25b recomputed from this JSON: match
record_hash sha256:664979df33c81cf3e531f8fbdc7bc14284b19c29a4f5b514e2f1d42519e2a34a recomputed from this JSON: match
from evidence-gold.json, 2 rows
| event_nameTEXT |
|---|
| Women's Soccer |
| Football game |
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:d600a85ebd7554e448ea060e2e2e20ec247fb1ec328a56c3d0cec33b46a0e8d6 recomputed from this JSON: match
record_hash sha256:6290b49c84c8b889ea04cb37f1a0c4c8b83e37a7de57219e8e18f856e04a2089 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 SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/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
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/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