R-SET NOT_EQUAL
debit_card_specializing · 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
What kind of currency did the customer paid at 16:25:00 in 2012/8/24?
the hint the set supplies: '2012/8/24' can be represented by '2012-08-24';
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 T3.Currency FROM transactions_1k AS T1 INNER JOIN gasstations AS T2 ON T1.GasStationID = T2.GasStationID INNER JOIN customers AS T3 ON T1.CustomerID = T3.CustomerID WHERE T1.Date = '2012-08-24' AND T1.Time = '16:25:00'this statement states no ordering of its own
sha256:b08acf9ce8d1711d12dc275035848bc24e10a0111c04ba8aa6845de0a0b33c93
SELECT Currency
FROM customers
JOIN transactions_1k ON customers.CustomerID = transactions_1k.CustomerID
WHERE transactions_1k.Time = '16:25:00' AND transactions_1k.Date = '2012-08-24';this statement states no ordering of its own
sha256:18c7812c48c88011c7265497269b1590425de582de351e83bbb5592d726eaecb
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 | CurrencyTEXT |
|---|---|
| no rows |
from counterexample.json, 2 rows, up to 25 shown per side, 1 on this page
| side | times | CurrencyTEXT |
|---|---|---|
| second | 2 | CZK |
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, 1 row
| CurrencyTEXT |
|---|
| CZK |
from counterexample.json, 3 rows
| CurrencyTEXT |
|---|
| CZK |
| CZK |
| CZK |
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:b08acf9ce8d1711d12dc275035848bc24e10a0111c04ba8aa6845de0a0b33c93",
"baseline_result": {
"columns": [
{
"name": "Currency",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "CZK"
}
]
],
"result_hash": "sha256:b08acf9ce8d1711d12dc275035848bc24e10a0111c04ba8aa6845de0a0b33c93"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"transactions_1k",
"gasstations",
"customers"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {
"yearmonth": 383282
},
"tables_not_reached_by_a_copy": {}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:b08acf9ce8d1711d12dc275035848bc24e10a0111c04ba8aa6845de0a0b33c93",
"result": {
"columns": [
{
"name": "Currency",
"declared_type": "TEXT"
}
],
"row_count": 1,
"truncated": false,
"rows_shown": 1,
"rows": [
[
{
"type": "str",
"value": "CZK"
}
]
],
"result_hash": "sha256:b08acf9ce8d1711d12dc275035848bc24e10a0111c04ba8aa6845de0a0b33c93"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT DISTINCT T3.Currency FROM transactions_1k AS T1 INNER JOIN gasstations AS T2 ON T1.GasStationID = T2.GasStationID INNER JOIN customers AS T3 ON T1.CustomerID = T3.CustomerID WHERE T1.Date = '2012-08-24' AND T1.Time = '16:25:00'result_hash sha256:b08acf9ce8d1711d12dc275035848bc24e10a0111c04ba8aa6845de0a0b33c93 recomputed from this JSON: match
record_hash sha256:dee4e142c44863168f0b0dbb0e00ec07aab224342d684a650616c0059da31044 recomputed from this JSON: match
from evidence-gold.json, 1 row
| CurrencyTEXT |
|---|
| CZK |
SELECT Currency
FROM customers
JOIN transactions_1k ON customers.CustomerID = transactions_1k.CustomerID
WHERE transactions_1k.Time = '16:25:00' AND transactions_1k.Date = '2012-08-24';result_hash sha256:18c7812c48c88011c7265497269b1590425de582de351e83bbb5592d726eaecb recomputed from this JSON: match
record_hash sha256:9030fb7963d1450de7cf513e56ba1038d26f0149cb71398d04d0ba37e30d3089 recomputed from this JSON: match
from evidence-second.json, 3 rows
| CurrencyTEXT |
|---|
| CZK |
| CZK |
| CZK |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-runs/data/minidev/dev_databases/debit_card_specializing/debit_card_specializing.sqlite | size=34635776 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/debit_card_specializing/debit_card_specializing.sqlite | size=34635776 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET