From: Alvaro Herrera <alvherre@commandprompt.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Benjamin Krajmalnik <kraj@servoyant.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: upper and UTF-8
Date: Mon, 26 Jul 2010 23:36:33 -0400
Message-ID: <1280201350-sup-1392@alvh.no-ip.org> (raw)
In-Reply-To: <AANLkTikRCdVyppWTztO1ocY9DBd1jQWPecG_K9yZLR6G@mail.gmail.com>
References: <F4E6A2751A2823418A21D4A160B689886147CA@fletch.stackdump.local>
<1280196392-sup-6027@alvh.no-ip.org>
<AANLkTikRCdVyppWTztO1ocY9DBd1jQWPecG_K9yZLR6G@mail.gmail.com>
Excerpts from Scott Marlowe's message of lun jul 26 23:12:08 -0400 2010:
> On Mon, Jul 26, 2010 at 8:09 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
> > I suspect that the problem is an incorrect client_encoding setting.
>
> Yeah, OP had set lc_collate to C under the mistaken impression that
> collation controlled the character sets you could insert into the
> database. If you create a db with lc_collate='C' then the upper only
> works on basic ascii characters near as I can tell.
Makes sense. The code seems to say that it's lc_ctype that's important
though, see str_toupper in formatting.c. So I think you could still set
collation to C and use a language-specific lc_ctype.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, scott.marlowe@gmail.com, kraj@servoyant.com
Subject: Re: upper and UTF-8
In-Reply-To: <1280201350-sup-1392@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox