-
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
executor: fix wrong behavior of set charset statement (#16984) #17289
executor: fix wrong behavior of set charset statement (#16984) #17289
Conversation
Signed-off-by: sre-bot <[email protected]>
/run-all-tests |
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.
pls fix the conflicts
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
Please run |
/run-all-tests |
@sre-bot merge failed. |
Signed-off-by: wjhuang2016 <[email protected]>
Signed-off-by: wjhuang2016 <[email protected]>
613db34
to
177f0a5
Compare
/merge |
/run-all-tests |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/run-all-tests |
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 |
cherry-pick #16984 to release-4.0
What problem does this PR solve?
Problem Summary:
Previously, we take
set charset
asset names
, and setcharsetCollation
too. However, it's wrong, as it's stated in hereWhat is changed and how it works?
Distinguish
set names
andset charset
statements and handle them differently.Related Parser PR.
Related changes
Check List
Tests
Side effects
Release note