Re: Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Different encoding for string values and identifier strings? Or (select 'tést' as tést) returns different values for string and identifier...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: francisco(at)npgsql(dot)org
Cc: Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Different encoding for string values and identifier strings? Or (select 'tést' as tést) returns different values for string and identifier...
Date: 2011-03-19 01:01:53
Message-ID: 27031.1300496513@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Francisco Figueiredo Jr." <francisco(at)npgsql(dot)org> writes:
> My database has encoding set to UTF-8 although my lc_collate is pt.BR.UTF-8
> this lc setting my have cause some trouble?

Hmmm ... actually, it strikes me that this may be a downcasing problem.
PG will try to feed an unquoted identifier through tolower(), and that
basically can't work on multibyte characters. Most implementations of
tolower() are smart enough to not change high-bit-set bytes in UTF8
locales, but maybe your platform's is not ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stefan Keller 2011-03-19 01:33:10 Insert value input syntax of an array of types without ARRAY/ROW nor casting?
Previous Message Tom Lane 2011-03-19 00:58:06 Re: error messages during restore