Use PostgreSQL unaccent extension und use it for user filters #14968
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.
https://community.openproject.org/work_packages/53371
I first looked at the ICU collations, but they have their own drackbacks, so I went to the
unaccent
core/contrib extension instead. We're currently not using and indexes on the concatenated user fields anyway, so the impact should not bee to bad. I've tested this on the public community dump for adequate sized user collection prior to filtering.See also for more information on ICU and different approaches and their drawbacks: https://stackoverflow.com/a/11007216/420614
Assigning to 13.5 due to the added migration