-
Notifications
You must be signed in to change notification settings - Fork 8k
Handle NULLs in ALTER MODIFY COLUMN #84770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Workflow [PR], commit [cd53684] Summary: ❌
|
antaljanosbenjamin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
23a2bdd to
ff270c5
Compare
f3140f1 to
238dcbb
Compare
6b5c46e to
6ab2401
Compare
Seems like #84881 |
|
Hi team, |
Hey! Did it broke in a way that is not mentioned in the changelog item? If yes, we have a problem. If not, then it is kind of expected. Unfortunately from time to time we have to bite the bullet to introduce backward incompatible changes in order to fix big issues, in this case stuck mutations. We try to keep backward incompatible changes minimal and try to always add a proper changelog item, however we might mistakes (not noticing backward incompatibility or missing parts of the scope). |
…umn_null_to_default Handle NULLs in ALTER MODIFY COLUMN
…umn_null_to_default Handle NULLs in ALTER MODIFY COLUMN
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
ALTER MODIFY COLUMN now requires explicit DEFAULT when converting nullable columns to non-nullable types. Previously such ALTERs could get stuck with cannot convert null to not null errors, now NULLs are replaced with column's default expression. Resolves #5985
Details
Close #5985