Fix read_schema
function for multi-column foreign key constaints
#476
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.
Update the query used by
read_schema
to fetch foreign key information. This fixes the problem ofcolumns
andreferencedColumns
containing duplicate entries for multi-column foreign keys.For a foreign key defined like
"fk_sellers" FOREIGN KEY (sellers_name, sellers_zip) REFERENCES sellers(name, zip)
the change in behaviour is as follows:Before:
After:
The solution here is to perform grouping and array aggregation of the referencing table's columns before the join to the referenced table's columns.
Fixes #475