For each dialect, the statements bind makes for a schema, loaded into a real engine, MUST make the tables, columns, nullability, primary keys, foreign keys, uniques, checks and indexes of the logical schema; the engine MUST refuse what the constraints forbid (a party related to itself, a second identifier of a kind, a code that is not in its list, a reference to a row that is not there), and a load of the reference data twice MUST leave the same rows.
Enforced (check): .github: cd commons/data && bun run verify — suite/physical-engines.test.ts: ${name}: the statements load, and the engine holds the tables, columns, nullability, primary keys and indexes of the logical schema; suite/physical-engines.test.ts: ${name}: the engine refuses what the constraints forbid and accepts what they allow; suite/physical-engines.test.ts: ${name}: the reference data is loaded, in the codes of the model it replaces, and loaded twice leaves the same rows
Proved by: data/suite/physical-engines.test.ts
Tests: passed: suite/physical-engines.test.ts duckdb: the reference data is loaded, in the codes of the model it replaces, and loaded tw; passed: suite/physical-engines.test.ts postgres: the reference data is loaded, in the codes of the model it replaces, and loaded ; passed: suite/physical-engines.test.ts sqlite: the reference data is loaded, in the codes of the model it replaces, and loaded tw; passed: suite/physical-engines.test.ts duckdb: the engine refuses what the constraints forbid and accepts what they allow; passed: suite/physical-engines.test.ts duckdb: the statements load, and the engine holds the tables, columns, nullability, primar and 4 more