-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
planner: fix different err msg from MySQL when group by window function #16134
Conversation
Codecov Report
@@ Coverage Diff @@
## master #16134 +/- ##
===========================================
Coverage 80.6129% 80.6129%
===========================================
Files 504 504
Lines 135936 135936
===========================================
Hits 109582 109582
Misses 17880 17880
Partials 8474 8474 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
@time-and-fate merge failed. |
/merge |
/run-all-tests |
/run-cherry-picker |
cherry pick to release-3.0 in PR #16161 |
cherry pick to release-3.1 in PR #16162 |
cherry pick to release-4.0 in PR #16165 |
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
What problem does this PR solve?
Issue Number: close #11518
Problem Summary: When GROUP BY is followed by a number in a select stmt and this number correspond to a window function in select fields, TiDB prints a different error message from MySQL.
What is changed and how it works?
What's Changed: When dealing with ast.PositionExpr in gbyResolver's Leave() method, we check if it's a ast.WindowFuncExpr. If so, ErrWrongGroupField will occur, which is expected.
Check List
Tests
Release Note