Fix USING column binding for right joins#345
Merged
Merged
Conversation
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
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.
What problem does this PR solve?
Fixes #326.
RIGHT/FULL OUTER JOIN ... USING (...)should bind unqualified USING column references to the visible merged column. Before this change,RIGHT JOIN ... USING(a) WHERE a = 4could bindato the left side and filter out right-only rows incorrectly.Issue link: #326
What is changed and how it works?
RIGHT JOIN ... USINGvisible columns to the right-side column.FULL JOIN ... USINGvisible columns ascoalesce(left, right).SELECT *duplicate-column hiding through the stored USING metadata.Code changes
Check List
Tests
Manual test steps:
Side effects
Note for reviewer
Full sqllogictest passed locally: 194 files.