And a 3rd reason to use ICU is that ICU supports a rich system of end-user customisation (see some simple examples in the PostgreSQL manual). While the ICU project's collation rules are based strictly on the Unicode Collation Algorithm and the ICU library version can be ma...
How will PostgreSQL react to this combo? A database cluster initdb:ed with locale=C/POSIX, and then a database in UNICODE (really utf-8) representation... hmm... I think I might have made a false assumption that the locale string would contain the character encoding. I do something ...
# For PostgreSQL, we can't trust a simple LOWER(column), with any collation, since # Postgres just defers to the C library which is different for each platform. The best # choice is the collkey function from pg_collkey which uses ICU to get a full unicode sort. # If that extension...
Setup used #1507 (comment) Infos [Mailer config] Host: redacted [Mailer config] Protocol: https:// Evaluated configuration: --- email: from: portus@example.com name: Portus reply_to: no-reply@example.com smtp: enabled: false address: smt...
And a 3rd reason to use ICU is that ICU supports a rich system of end-user customisation (see some simple examples in thePostgreSQL manual). While the ICU project's collation rules are based strictly on theUnicode Collation Algorithmand the ICU library version c...