-
Notifications
You must be signed in to change notification settings - Fork 563
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
Not work case insensitive #820
Comments
Hi @antoxi4. Thanks for reaching out. We're working through a bit of backlog and will be in touch with a solution or follow-up questions soon. Cheers! :) |
Hi @antoxi4 sorry, sorting and case insensitive string matches in queries are only supported for character sets in ‘Latin Basic’, ‘Latin Supplement’, ‘Latin Extended A’, ‘Latin Extended B’ (UTF-8 range 0-591). |
@kristiandupont Are you going to support Cyrillic in the future? This is very important for applications which use this character set. |
Is there a solution to this problem? How can I get around this? |
why closed the task without a correct answer, the task is relevant and important not only for me! |
@dimlksin2 You are welcome to create another issue with a request to support it. But just to set expectations, it's not trivial to do as it requires us to include a big ICU library. |
I try filter items with this query
items.filtered('actualName CONTAINS[c] $0', 'паркова');
and items result is zero. but if i change query string for
items.filtered('actualName CONTAINS[c] $0', 'Паркова');
then result is right.
RN 0.38
IOS, ANDROID.
Realm 0.15.4
The text was updated successfully, but these errors were encountered: