Uh oh!
There was an error while loading. Please reload this page.
Add test case for incorrect FULL OUTER JOIN + LIMIT pushdown @alamb - #14336
Closed
alamb wants to merge 2 commits into
Closed
Add test case for incorrect FULL OUTER JOIN + LIMIT pushdown @alamb#14336alamb wants to merge 2 commits into
alamb wants to merge 2 commits into
Conversation
alamb
commented
Jan 28, 2025
ContributorAuthor
Subsumed by #14338 |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Which issue does this PR close?
FULL OUTER JOINandLIMITproduces wrong results #14335Rationale for this change
I wrote these test cases finding the bug, so I wanted to assist in fixing them
What changes are included in this PR?
Add tests for limit + outer joins
Are these changes tested?
They are only tests
Are there any user-facing changes?