-
Notifications
You must be signed in to change notification settings - Fork 427
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
feat: Table Column Defaults #631
feat: Table Column Defaults #631
Conversation
/ok-to-test sha=a654ce1 |
Integration tests failure for a654ce1 |
@alldoami - I've corrected the failed TestSequenceRead unit test; some of the other unit tests I can't run locally just to account level conflicts we already have enabled, e.g. SCIM. |
/ok-to-test sha=85a1a43 |
Integration tests failure for 85a1a43 |
Looks like there is a |
@alldoami - sorted. I hadn't correctly accounted for new columns being added without a default value 🤦 . Working now
|
/ok-to-test sha=0ef8734 |
Integration tests failure for 0ef8734 |
@alldoami - anything in the logs to suggest what else needs correcting? |
/ok-to-test sha=8fc3a2b |
Integration tests success for 8fc3a2b |
Add support for column defaults on the
snowflake_table
resource. Note there are some limitations:ALTER TABLE MODIFY COLUMN
does not support adding a default; unless a sequence has been used originally as the default and a new sequence is being usedALTER TABLE ADD COLUMN
only supports setting a column default to a constant valueTest Plan
make docs
References