Repository navigation
minor: Remove null_equals_null todo comment - #16045
Closed
jonathanc-n wants to merge 2 commits into
Closed
jonathanc-n wants to merge 2 commits into
jonathanc-n wants to merge 2 commits into
Conversation
Contributor
|
Doesn't it make a difference for |
Contributor
|
I would still keep it. |
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.
Rationale for this change
While looking through the join implementations, I noticed that
null_equals_nullwas marked for todo. Physical planner will not call on NestedLoopJoin if there is an equi condition.