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 PR aims to fix an issue with getting the wrong unique constraints from a table.
You can reproduce the issue by doing the following:
SCHEMA_A
SCHEMA_A.TABLE
with a constraint such asCONSTRAINT_NAME UNIQUE(COL1, COL2)
SCHEMA_B
SCHEMA_B.TABLE
with a constraint such asCONSTRAINT_NAME UNIQUE(COL1, COL3)
*Important, the constraint name must be the same.With that setup, if you run the query you can see that for both
SCHEMA_A.TABLE
andSCHEMA_B_TABLE
you will find the constraint being: COL1, COL2, COL1, COL3.This happens because we're doing a cross join and filtering only by the constraint name.
The PR changes the Query to actually do a join on:
in order to avoid this issue