Recognises greenfield DDL aimed at a populated database

Mida see tähendab

`08-ddl/` handed to a release for an environment that already has data. This output builds a schema from nothing. The changes that look smallest in the diff are the ones that need a backfill plan — a nullable column tightened to `NOT NULL`, a widened or narrowed type, a split column — and on Databricks `ALTER TABLE ... ADD CONSTRAINT` validates the existing rows and fails on the first violation.

Kuidas seda hinnatakse

Flags the deficient case and passes the acceptable one. Deficient: `account_number` tightened to `NOT NULL` in the model and the regenerated DDL given to the release; 3 % of migrated accounts have no IBAN, the deploy fails halfway, and the schema is left with half its constraints applied Acceptable: The regenerated DDL diffed against the previous version as the statement of intent, and the migration hand-written for that diff where deployment lives (Flyway, Liquibase, dbt, Alembic) with backfill and rollback — then verified by rebuilding an empty database from the generated DDL and comparing it with the migrated one

Tugineb

Explains schema migration and rollbackK-857 · Teadmine

Vajalik

Puudub