Uh oh!
There was an error while loading. Please reload this page.
[main] Fix to #32062 - Altering a nullable column to not null generates invalid SQL commands for migration - #32102
Merged
Merged
Conversation
…lid SQL commands for migration Problem was that alter column from nullable to non-nullable on a temporal table requires us to disable versioning, so that null values could be properly updated to the new defaults. Fixes#32062
roji
approved these changes
Oct 23, 2023
1 task
1 task
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem was that alter column from nullable to non-nullable on a temporal table requires us to disable versioning, so that null values could be properly updated to the new defaults.
Fixes#32062