From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Wrong results using initcap() with non normalized string |
Date: | 2019-09-21 00:42:51 |
Message-ID: | 20190921004251.GA18370@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-Sep-20, Tom Lane wrote:
> =?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo(dot)santamaria(at)gmail(dot)com> writes:
> > I have come around a strange situation when using a unicode string
> > that has non normalized characters. The attached script 'initcap.sql'
> > can reproduce the problem.
For illustration purposes:
SELECT initcap('ŞUB');
initcap
─────────
Şub
(1 fila)
SELECT initcap('ŞUB');
initcap
─────────
ŞUb
(1 fila)
> If we're going to start worrying about non-normalized characters,
> I suspect there are far more places than this one that we'd have
> to consider buggy :-(.
I would think that we have to start somewhere, rather than take the
position that we can never do anything about it.
(ref: https://www.postgresql.org/message-id/flat/53E179E1.3060404%402ndquadrant.com )
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-09-21 02:16:59 | Re: subscriptionCheck failures on nightjar |
Previous Message | Alvaro Herrera | 2019-09-21 00:09:31 | Re: Optimization of some jsonb functions |