v1.2.2 — a reader's comment against a fully covered test suite

A new post, "A forum comment found a bug that 100% coverage did not".

A reader in a comment thread asked how one create-table form reconciles SQL Server's identity checkbox with PostgreSQL's sequences. It did not: the form carried a dbType prop it never read, so every engine got PostgreSQL's DDL. On SQL Server, Oracle and Trino that failed loudly. On SQLite and libSQL it succeeded and handed people a primary key that accepts NULLs, which is the version of the bug worth reading about.

The post shows the column clause each of the eight engines now gets, including the two that cannot be spelled at all: DuckDB needs a sequence and two statements, and Trino is offered no auto-increment, no primary key and no unique constraint because its grammar has none. It also explains why a suite with 100% line coverage had nothing to say: every test mounted the form with the engine already known, and the application never does that.

Two defects found while verifying against live engines are named and left open rather than written around, and the missing ALTER COLUMN forms are stated as missing.