planner: resolveFromPlan when tblName.colName exists in having clause (#18349) #18433
Conversation
This file contains 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
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
/run-all-tests |
ti-srebot
added
sig/planner
qw4990
reviewed
Jul 24, 2020
Comment on lines
+1412
to
+1415
| <<<<<<< HEAD | ||
| if a.orderBy { | ||
| index, a.err = a.resolveFromSchema(v, a.p.Schema()) | ||
| ======= |
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.
cherry-pick #18349 to release-3.1
What problem does this PR solve?
Issue Number: close #18384
Problem Summary:
What is changed and how it works?
What's Changed:
For SQL like
select a+1 from t having t.a, we need to resolve it from the plan and select fields both.How it Works:
Related changes
Check List
Tests
Side effects
N/A
Release note
select a from t having t.a