R-SET NOT_EQUAL
questions
What elements are in a double type bond?
the hint the set supplies: double type bond refers to bond_type = '=';
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 T1.element FROM atom AS T1 INNER JOIN bond AS T2 ON T1.molecule_id = T2.molecule_id INNER JOIN connected AS T3 ON T1.atom_id = T3.atom_id WHERE T2.bond_type = '='this statement states no ordering of its own
sha256:029fb5dbc54b4b7234684a95a9d6e26ec41b884c6e7ce239fabb69a0ae9d6764
SELECT DISTINCT T1.element FROM atom AS T1 JOIN connected AS T2 ON T1.atom_id = T2.atom_id JOIN bond AS T3 ON T2.bond_id = T3.bond_id WHERE T3.bond_type = '='this statement states no ordering of its own
sha256:9d2e4c969dafd20791a3829f3bbd056403b619bcedd6a6105e58228c98fa2bee
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, 1 row, up to 25 shown per side
| side | elementTEXT |
|---|---|
| gold | n |
from counterexample.json, 0 rows, up to 25 shown per side
| side | elementTEXT |
|---|---|
| no rows |
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, 3 rows
| elementTEXT |
|---|
| c |
| o |
| n |
from counterexample.json, 2 rows
| elementTEXT |
|---|
| c |
| o |
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:029fb5dbc54b4b7234684a95a9d6e26ec41b884c6e7ce239fabb69a0ae9d6764",
"baseline_result": {
"columns": [
{
"name": "element",
"declared_type": "TEXT"
}
],
"row_count": 3,
"truncated": false,
"rows_shown": 3,
"rows": [
[
{
"type": "str",
"value": "c"
}
],
[
{
"type": "str",
"value": "o"
}
],
[
{
"type": "str",
"value": "n"
}
]
],
"result_hash": "sha256:029fb5dbc54b4b7234684a95a9d6e26ec41b884c6e7ce239fabb69a0ae9d6764"
},
"planner_statistics": {},
"shuffle": {
"seed": "1",
"row_limit": 300000,
"tables": [
"atom",
"bond",
"connected"
],
"tables_not_shuffled": [],
"tables_skipped_for_size": {},
"tables_not_reached_by_a_copy": {
"main.y": "the statement names this table's schema, and a name that states its schema is read from that schema whatever TEMP holds, so the rerun reads this table and not a copy of it"
}
},
"shuffled_copies": {
"run": true,
"verdict": "equal",
"differs": false,
"result_hash": "sha256:029fb5dbc54b4b7234684a95a9d6e26ec41b884c6e7ce239fabb69a0ae9d6764",
"result": {
"columns": [
{
"name": "element",
"declared_type": "TEXT"
}
],
"row_count": 3,
"truncated": false,
"rows_shown": 3,
"rows": [
[
{
"type": "str",
"value": "c"
}
],
[
{
"type": "str",
"value": "o"
}
],
[
{
"type": "str",
"value": "n"
}
]
],
"result_hash": "sha256:029fb5dbc54b4b7234684a95a9d6e26ec41b884c6e7ce239fabb69a0ae9d6764"
}
},
"plan_variant": {
"run": false,
"reason": "the plan variant was not asked for"
}
}SELECT DISTINCT T1.element FROM atom AS T1 INNER JOIN bond AS T2 ON T1.molecule_id = T2.molecule_id INNER JOIN connected AS T3 ON T1.atom_id = T3.atom_id WHERE T2.bond_type = '='result_hash sha256:029fb5dbc54b4b7234684a95a9d6e26ec41b884c6e7ce239fabb69a0ae9d6764 recomputed from this JSON: match
record_hash sha256:8fa0613e80eadb7a86bab18324390df7f5fe73f783a8872be232188e44b5b1d4 recomputed from this JSON: match
from evidence-gold.json, 3 rows
| elementTEXT |
|---|
| c |
| o |
| n |
SELECT DISTINCT T1.element FROM atom AS T1 JOIN connected AS T2 ON T1.atom_id = T2.atom_id JOIN bond AS T3 ON T2.bond_id = T3.bond_id WHERE T3.bond_type = '='result_hash sha256:9d2e4c969dafd20791a3829f3bbd056403b619bcedd6a6105e58228c98fa2bee recomputed from this JSON: match
record_hash sha256:ab35b97982375492955a541eec9032c857d8e95c73b30ef52a7495337556bc5e recomputed from this JSON: match
from evidence-second.json, 2 rows
| elementTEXT |
|---|
| c |
| o |
re-run this statement read-only against SQLite 3.53.4 | file=/private/tmp/attestql-site-sandbox/demo/fixture.sqlite | size=69632 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-site-sandbox/demo/fixture.sqlite | size=69632 under the session settings and over the data this record's fixture digest names, and compare the two results under R-SET