Fix 5330 add Postgresql ILIKE operator #5333
Merged
Conversation
This file contains hidden or 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
Add `ILIKE` to `binary_like_operator` Postgresql doesn't use `GLOB | REGEXP | MATCH` keywords It would require rewriting the mixin just to add `ILIKE` Add like and ilike patterns to regex_match_operator regex_match_operator is ordered by shortest matching characters first as the parser gets confused
JakeWharton
approved these changes
Jul 8, 2024
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.
fixes #5330
https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-LIKE
ILIKEoperator - extended existing rule even though it has Sqlite operators GLOB, MATCH, REGEX,~~is equivalent to LIKE, and~~*corresponds to ILIKE. There are also!~~and!~~*operatorsthat represent NOT LIKE and NOT ILIKE