Skip site navigation (1) Skip section navigation (2)

Re: upper and UTF-8

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Benjamin Krajmalnik <kraj(at)servoyant(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: upper and UTF-8
Date: 2010-07-27 03:36:33
Message-ID: 1280201350-sup-1392@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-admin
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(at)commandprompt(dot)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.

In response to

pgsql-admin by date

Next:From: Lazarin ToniDate: 2010-07-27 10:37:17
Subject: postgresql basic info
Previous:From: Scott MarloweDate: 2010-07-27 03:12:08
Subject: Re: upper and UTF-8

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group