planner: fix wrong behavior for = all() (#52801) #53255
Open
+397
−3
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 is an automated cherry-pick of #52801
What problem does this PR solve?
Issue Number: close #52755
Problem Summary:
What changed and how does it work?
Use
max
function instead offirst_row
function.if the query is
t.id = all (select s.id from s)
, it will be rewrote tot.id = (select s.id from s having count(distinct s.id) <= 1 and [all checker])
.If there is NULL in the
s.id
column, s.id should be the value that isn't null in condition t.id == s.id. So use function max to filter NULL.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.