From: | "Benjamin Krajmalnik" <kraj(at)servoyant(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: upper and UTF-8 |
Date: | 2010-07-26 21:18:15 |
Message-ID: | F4E6A2751A2823418A21D4A160B689886147CB@fletch.stackdump.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
CREATE DATABASE ishield
WITH OWNER = postgres
ENCODING = 'UTF8'
LC_COLLATE = 'C'
LC_CTYPE = 'C'
CONNECTION LIMIT = -1;
> -----Original Message-----
> From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
> Sent: Monday, July 26, 2010 3:17 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] upper and UTF-8
>
> On Mon, Jul 26, 2010 at 3:03 PM, Benjamin Krajmalnik
> <kraj(at)servoyant(dot)com> wrote:
> > I just used the upper(text) function on a database which is utf8
> encoded and
> > which has spanish text.
> >
> > All of the regular characters were properly converted, except for
> characters
> > which had accents.
>
> What are your various LC_* variables for that database?
>
> --
> To understand recursion, one must first understand recursion.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-07-26 21:39:09 | Re: upper and UTF-8 |
Previous Message | Scott Marlowe | 2010-07-26 21:17:16 | Re: upper and UTF-8 |