Squash the migration chain into one baseline - #185
Merged
Conversation
The 19-revision chain collapses into a single create-all baseline that reuses the old head's revision id, so an installation already at head needs no stamp and a fresh install runs one migration. Data migrations vanish with the chain: they rewrote rows no fresh database has, and the system account they seeded comes from seed_system_account at startup. Schema proven identical to the full chain applied (pg_dump -s diff). test_plan_gate_migration goes with the mid-chain revision it pinned.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 19-revision chain collapses into a single create-all baseline that reuses the old head's revision id (
d9f3a7c1e5b2): an installation already at head needs no stamp, and a fresh install runs one migration.The chain's data migrations vanish with it — they rewrote rows no fresh database has. The one seed they carried, the
systemaccount, is created byseed_system_accountat startup, so the baseline stays pure schema.Schema proven identical to the full chain applied:
pg_dump --schema-onlyof a chain-migrated database and a baseline-migrated database diff clean, column order and constraint names included.downgrade()runs to base cleanly.test_plan_gate_migrationis deleted with the mid-chain revision it pinned; the extension-migration tests run under their own version tables and are untouched.