You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The implementation would only optimize only if search text is either: %foo% (substring), %foo (suffix), or foo% (prefix) search. Otherwise the implementation would fall back to the Postgres built-in LIKE search automatically.
Possible gotchas:
%_foo% would not be supported, since _ means "matches any 1 character"
%\_foo% is supported, since the backslash escapes the _.
The text was updated successfully, but these errors were encountered:
This is a possible proposal to implement:
stringtheory.like(haystack text, search text) -> boolean
The implementation would only optimize only if search text is either:
%foo%
(substring),%foo
(suffix), orfoo%
(prefix) search. Otherwise the implementation would fall back to the Postgres built-inLIKE
search automatically.Possible gotchas:
%_foo%
would not be supported, since_
means "matches any 1 character"%\_foo%
is supported, since the backslash escapes the_
.The text was updated successfully, but these errors were encountered: