SNOW-922868 Preserve the sequence order of foreign keys when dealing with composite keys#449
Open
skp33 wants to merge 2 commits intosnowflakedb:mainfrom
Open
SNOW-922868 Preserve the sequence order of foreign keys when dealing with composite keys#449skp33 wants to merge 2 commits intosnowflakedb:mainfrom
skp33 wants to merge 2 commits intosnowflakedb:mainfrom
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
skp33
changed the title
Author
|
recheck |
Author
|
I have read the CLA Document and I hereby sign the CLA |
Author
|
Can anyone please take a look at this? |
|
having the same issue... |
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 free
to 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.
This MR has a fix for #450 (Preserve the sequence order of foreign keys when dealing with composite keys.)
I am reordering foreign keys based on the sequence key field.