Repository navigation
Make PostgresModelDataMigrator work for scheduled rebuilds of a table - #289
Merged
Merged
Conversation
db_constraint=FalsePostgresModelDataMigrator work for scheduled rebuilds of a table
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.
Don't clone the foreign key constraint of a field with
db_constraint=False.clone_model_constraints_and_indexes_to_schemalooked up a constraint that does not exist and the unpack raised aValueError, so the migrator could not migrate such a model at allDelete the work and backup schemas when a phase fails. They were left behind, half-filled, on every failed migration
Add
keep_backup_schema, default on. Turned off, the backup schema is deleted after a successful migration, so a migration that runs every day does not leave a copy of the table behind on every runMove the CI images from bullseye to bookworm. The bullseye security packages are gone from the Debian mirrors, so installing packages failed every job
Fix
release.ymlnot parsing, which failed a run on every push and would have failed a release. Its version check also used[[, which the container's defaultshdoes not have