From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Rajanikant Chirmade <rajanikant(dot)chirmade(at)enterprisedb(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: multibyte-character aware support for function "downcase_truncate_identifier()" |
Date: | 2010-07-26 12:20:00 |
Message-ID: | AANLkTimEZfcfFS4ANKpaxK05xP+XN36ecws-B4pux11Z@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 26, 2010 at 12:40 AM, Rajanikant Chirmade
<rajanikant(dot)chirmade(at)enterprisedb(dot)com> wrote:
> Since discussion stopped in discussion thread
>
> http://archives.postgresql.org/pgsql-bugs/2006-09/msg00128.php
>
> Are there any implications of this change in handling identifiers ?
>
> Thanks & Regards,
> Rajanikant Chirmade
An even more relevant message appears to be this one:
http://archives.postgresql.org/pgsql-bugs/2006-09/msg00133.php
Both this and the comment in downcase_truncate_identifier() suggests
that the current method is attributable to lack of support for
Unicode-aware case normalization and is known not to work correctly in
all locales. Locale and encoding stuff isn't really my area of
expertise, but if now have support for Unicode-aware case
normalization, shouldn't we be using it here, too?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-07-26 12:52:46 | Re: dynamically allocating chunks from shared memory |
Previous Message | Robert Haas | 2010-07-26 12:02:44 | Re: patch (for 9.1) string functions |