-
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
expression: support collation for REGEXP function #17255
Conversation
Codecov Report
@@ Coverage Diff @@
## master #17255 +/- ##
===========================================
Coverage 79.7429% 79.7429%
===========================================
Files 522 522
Lines 142133 142133
===========================================
Hits 113341 113341
Misses 19780 19780
Partials 9012 9012 |
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 |
@wjhuang2016 merge failed. |
/merge |
/run-all-tests |
@wjhuang2016 merge failed. |
/merge |
/run-all-tests |
@wjhuang2016 merge failed. |
/run-unit-test |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-4.0 in PR #17581 |
What problem does this PR solve?
Issue Number: close #17094
Problem Summary:
Previously, we didn't handle collation when builds the REGEXP function.
What is changed and how it works?
If the collation is case-insensitive, we compile it by
regexp.Compile("(?i)" + pat)
.If not, we compile it by
regexp.Compile
Related changes
Check List
Tests
Side effects
Release note