Fix Unicode case-insensitive search for keyword queries #6224
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.
Problem
The original implementation used the
LIKEoperator for case-insensitive search which only supports case-insensitive matching for ASCII characters (A-Z), not Unicode. SQLite'sLOWER()function also lacks Unicode support, so it wouldn't solve the problem. This caused searches to be case-sensitive for non-English content.Example:
Solution
Use custom SQLite function
lower_unicode()that uses Go'sstrings.ToLower()for proper Unicode case folding. All keyword search queries now use this function to ensure truly case-insensitive matching across all character sets.