-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
expression: do not rewrite like
to =
if new collation is enabled
#21893
Conversation
# Conflicts: # expression/integration_test.go
/run-all-tests |
there are some reasons to rewrite |
like
to =
if pattern has no wildcardlike
to =
if pattern has no wildcard and new collation is enabled
like
to =
if pattern has no wildcard and new collation is enabledlike
to =
if new collation is enabled
@winoros @wjhuang2016 PTAL |
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
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@xiongjiwei merge failed. |
/merge |
/run-all-tests |
/label needs-cherry-pick-4.0 |
/run-cherry-pick |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #22531 |
…21893) (#22531) Signed-off-by: ti-srebot <[email protected]>
What problem does this PR solve?
Issue Number: close #21892
like
function and=
are different if usingutf8mb4_unicode_ci
collation even if the pattern does not has wildcard. so we cannot rewritelike
to=
if new collation is enabled.see also operator_like
Check List
Tests
Release note
like
function returns the wrong result when using collation