Postgres Pro
Downloads
Home   >   mailing lists

Re: Wrong results using initcap() with non normalized string - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Wrong results using initcap() with non normalized string
Date
Msg-id 7126.1569021600@sss.pgh.pa.us
Whole thread Raw
In response to Wrong results using initcap() with non normalized string  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: Wrong results using initcap() with non normalized string
List pgsql-hackers
Tree view 
=?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= <juanjo.santamaria@gmail.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.
> The attached patch can fix the issue.

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 :-(.

As for the details of the patch, it seems overly certain that
it's working with UTF8 data.

            regards, tom lane

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: backup manifests
Next
From: Tom Lane
Date:
Subject: Re: Nondeterministic collations vs. text_pattern_ops