Prev: keepalive in libpq using
Next: [HACKERS] pg_dump and join aliases (was Re: [BUGS] ERROR: cannot handle unplanned sub-select)
From: Tom Lane on 7 Jul 2010 10:07
Rajanikant Chirmade <rajanikant.chirmade(a)enterprisedb.com> writes:
> Every identifier is downcase & truncated by function
> "downcase_truncate_identifier()"
> before using it.

> But since the function "downcase_truncate_identifier()" is not
> multibyte-charecter aware,
> it is not able to downcase some of special charecters in identifier like
> "my_Schem�".

IIRC this is intentional. Please consult the archives for previous
discussions.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Rajanikant Chirmade on 13 Jul 2010 03:10
On Wed, Jul 7, 2010 at 7:37 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:

> Rajanikant Chirmade <rajanikant.chirmade(a)enterprisedb.com> writes:
> > Every identifier is downcase & truncated by function
> > "downcase_truncate_identifier()"
> > before using it.
>
> > But since the function "downcase_truncate_identifier()" is not
> > multibyte-charecter aware,
> > it is not able to downcase some of special charecters in identifier like
> > "my_SchemÄ".
>
>




> IIRC this is intentional. Please consult the archives for previous
> discussions.
>
> regards, tom lane
>



I got one discussion thread on same issue. But it stopped without any
conclusion.

http://archives.postgresql.org/pgsql-bugs/2006-09/msg00128.php

Thanks & Regards,
Rajanikant Chirmade.
From: Rajanikant Chirmade on 26 Jul 2010 00:40
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

On Tue, Jul 13, 2010 at 12:10 AM, Rajanikant Chirmade <
rajanikant.chirmade(a)enterprisedb.com> wrote:

>
>
> On Wed, Jul 7, 2010 at 7:37 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
>
>> Rajanikant Chirmade <rajanikant.chirmade(a)enterprisedb.com> writes:
>> > Every identifier is downcase & truncated by function
>> > "downcase_truncate_identifier()"
>> > before using it.
>>
>> > But since the function "downcase_truncate_identifier()" is not
>> > multibyte-charecter aware,
>> > it is not able to downcase some of special charecters in identifier like
>> > "my_SchemÄ".
>>
>>
>
>
>
>
>> IIRC this is intentional. Please consult the archives for previous
>> discussions.
>>
>> regards, tom lane
>>
>
>
>
> I got one discussion thread on same issue. But it stopped without any
> conclusion.
>
> http://archives.postgresql.org/pgsql-bugs/2006-09/msg00128.php
>
> Thanks & Regards,
> Rajanikant Chirmade.
>
>
>
>
From: Robert Haas on 26 Jul 2010 08:20
On Mon, Jul 26, 2010 at 12:40 AM, Rajanikant Chirmade
<rajanikant.chirmade(a)enterprisedb.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

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: keepalive in libpq using
Next: [HACKERS] pg_dump and join aliases (was Re: [BUGS] ERROR: cannot handle unplanned sub-select)