| From: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com> |
|---|---|
| To: | Jakob(dot)Witczak(at)dlr(dot)de |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: German "umlaut insensitive" query |
| Date: | 2019-09-20 12:17:15 |
| Message-ID: | DA29F2FD-A2DC-4CA0-81D5-283D9A17B548@excoventures.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> On Sep 20, 2019, at 4:36 AM, <Jakob(dot)Witczak(at)dlr(dot)de> <Jakob(dot)Witczak(at)dlr(dot)de> wrote:
>
> Hi,
>
> i found an entry from 2004, where it is about the German Umlaute and i have the same problem.
> https://www.postgresql.org/message-id/4135E7F5.4070002%40stroetgen.de <https://www.postgresql.org/message-id/4135E7F5.4070002%40stroetgen.de>
>
> I also found this article:
> https://dba.stackexchange.com/questions/195502/postgres-collate-example-in-select <https://dba.stackexchange.com/questions/195502/postgres-collate-example-in-select>
>
> Are there other possibilities today (for example COLLATE) besides replace() to process the German Umlaute?
> In the long term, we also want to use it for other countries.
There is a feature in the upcoming PostgreSQL 12 release that
allows for accent insensitive queries:
https://www.postgresql.org/docs/12/collation.html#COLLATION-NONDETERMINISTIC <https://www.postgresql.org/docs/12/collation.html#COLLATION-NONDETERMINISTIC>
This is part of PostgreSQL’s support for ICU collations.
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | intmail01@gmail.com | 2019-09-20 22:20:42 | Dialog box, passing parameter fails |
| Previous Message | Jakob.Witczak | 2019-09-20 08:36:49 | German "umlaut insensitive" query |