For a dialect that says how a table is made again, a change of whether a column may be null, of a default, of the primary key, of a constraint that is not an index, or a column that is required and has no default, MUST be made by making the table again: the statements the dialect needs first, a table of the state after the change under a name of its own, the rows of the columns the two tables have in common copied into it, the old table dropped, the new one renamed to the old name, and the indexes made.
Enforced (check): .github: cd commons/data && bun run verify — suite/rewrite.test.ts: on SQLite a key is added by making the table again, the rows and what refers to the table are kept, the new definition is enforced, and the step says what it is; suite/rewrite.test.ts: a column made required is made by making the table again where the engine cannot, a row that does not meet it rolls the step back whole, and it succeeds once the row does; suite/rewrite.test.ts: the statements are written from the states: the indexes are made after, the primary key is kept, and a column the tables have in common is copied
Proved by: data/suite/rewrite.test.ts
Tests: passed: suite/rewrite.test.ts on SQLite a key is added by making the table again, the rows and what refers to the table ; passed: suite/rewrite.test.ts the statements are written from the states: the indexes are made after, the primary key is; passed: suite/rewrite.test.ts a column made required is made by making the table again where the engine cannot, a row th