Add volatile default requires full table rewrite hazard #258
+103
−26
Conversation
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
Adding a new NOT NULL column usually needs a backfill. This change adds a hazard and shows a suggested online migration path (add nullable -> backfill -> set NOT NULL).
bplunkett-stripe
force-pushed
the
bplunkett/new-column-requires-backfill
branch
3 times, most recently
from
df2bdee to
8bacee2
Compare
bplunkett-stripe
force-pushed
the
bplunkett/new-column-requires-backfill
branch
from
8bacee2 to
c3ce8aa
Compare
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.
Description
This is a continuation of #254 tweaked to be slightly more correct.
Thank you @catatsuy for the contribution!
Motivation
Safer migrations
Testing
Via unit tests