ranger: check the collation when checking like func (#16380) #16783
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
|
/run-all-tests |
ghost
requested a review
from 
|
/run-integration-copr-test |
1 similar comment
|
/run-integration-copr-test |
SunRunAway
approved these changes
Apr 26, 2020
SunRunAway
added
the
status/can-merge
|
/run-all-tests |
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 #16380 to release-4.0
What problem does this PR solve?
Issue Number: close #15988
Problem Summary:
We didn't check the LIKE func's collation when checking whether it can be used to build range.
What is changed and how it works?
What's Changed:
Check the collation info, and if the LIKE's collation info is different with the column's.
Don't use it to build range.
Related changes
Check List
Tests