From: Benjamin Krajmalnik <kraj@servoyant.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: upper and UTF-8
Date: Mon, 26 Jul 2010 15:18:15 -0600
Message-ID: <F4E6A2751A2823418A21D4A160B689886147CB@fletch.stackdump.local> (raw)
In-Reply-To: <AANLkTi=EeD8YZd9T1FaTGZOVGsSWzZEoog7R+Xc63HYT@mail.gmail.com>
References: <F4E6A2751A2823418A21D4A160B689886147CA@fletch.stackdump.local>
<AANLkTi=EeD8YZd9T1FaTGZOVGsSWzZEoog7R+Xc63HYT@mail.gmail.com>
CREATE DATABASE ishield
WITH OWNER = postgres
ENCODING = 'UTF8'
LC_COLLATE = 'C'
LC_CTYPE = 'C'
CONNECTION LIMIT = -1;
> -----Original Message-----
> From: Scott Marlowe [mailto:scott.marlowe@gmail.com]
> Sent: Monday, July 26, 2010 3:17 PM
> To: Benjamin Krajmalnik
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] upper and UTF-8
>
> On Mon, Jul 26, 2010 at 3:03 PM, Benjamin Krajmalnik
> <kraj@servoyant.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.
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: kraj@servoyant.com, scott.marlowe@gmail.com
Subject: Re: upper and UTF-8
In-Reply-To: <F4E6A2751A2823418A21D4A160B689886147CB@fletch.stackdump.local>
* 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