Topic
Versioned, reviewed scripts that incrementally change a database's table structure, used as the controlled alternative to automatic schema sync at startup.
MariaDB rebuilt a 320 MB table for a plain ADD COLUMN and blocked a write for over 30 seconds when a FULLTEXT key was present, a dev.to test found. An identical table without the index took 60 milliseconds.
Reality
Postgres locks both tables with SHARE ROW EXCLUSIVE when a migration adds a foreign key, blocking writes until every child row is scanned. A dev.to guide on Laravel migrations splits the change into two statements so the slow scan stops holding up the app's writes.
Reality
Drizzle-kit generated a DROP TABLE ... CASCADE for a table still in production when a developer asked it for two new tables. The developer traces it to schema.ts, drizzle-kit's snapshot and the live database each describing a different schema.
Reality
SQLite 3.53's ALTER COLUMN SET NOT NULL made six write calls in a developer's test, where the copy-and-rename rebuild made 69,843. The null check stays cheap only if the column is indexed, and Ubuntu's packaged 3.45.1 cannot parse the statement.
Reality
Schemity's developer found SQLite's usual column-type rebuild deleted all three child rows because its PRAGMA ran inside the transaction. A safe version sets the foreign-key switch before BEGIN and checks the copied values before dropping the old table.
Reality
Many SvelteKit starter kits run Drizzle migrations on every boot, a default that turns into a race once two replicas start at the same moment. A dev.to post moves the writes into one explicit step before traffic and keeps the boot call as a backstop.
Reality
One developer shipping Drizzle ORM on two SvelteKit kits keeps drizzle-kit push in prototyping because it writes no migration history. Production gets generated SQL that is read before it runs, plus a boot-time migrate that multiple replicas can race.
Reality
One NocoBase user diffed a 2.1.39-to-2.2.14 upgrade on PostgreSQL 16 and found 44 new columns, only two of them on existing tables. The same test shows admin-built pages live in flowModels, so any upgrade check has to hash that table's JSON before and after.
Reality
A dev.to field report traces migration outages to the order in which Postgres grants locks, and prescribes a lock_timeout of a few seconds plus a three-deploy expand, backfill and contract sequence for every breaking change.
Reality
A pass over one security suite turned up three patterns that never fail at runtime and sink a procurement read anyway. The arithmetic on the compose file is the interesting part.
Reality