Fix columnNames snapshot attribute of uniqueConstraints for Snowflake #3123
Conversation
This file contains 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
nvoxland
approved these changes
Aug 1, 2022
KushnirykOleh
approved these changes
Aug 2, 2022
yodzhubeiskyi
changed the title
suryaaki2
approved these changes
Aug 2, 2022
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.
Impact
Description
INFORMATION_SCHEMA in Snowflake doesn’t track ‘column_name’ attribute for constraints. As result, uniqueConstraints snapshot and changesets produced from diff/generate-changelog commands contain columnNames=”” attribute which results in Error during following update command. Currently the best workaround to get column_name for constraint is to use SHOW UNIQUE KEYS command followed by result_scan(last_query_id()) function.