From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Benjamin Krajmalnik <kraj(at)servoyant(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: upper and UTF-8 |
Date: | 2010-07-26 21:39:09 |
Message-ID: | AANLkTimgeBFoRW=xDO_aXnhjmcKhLQWWfFT43X3Deb_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I'd try creating a db with en_US or even better whatever is spanish
encoding for lc_collate and see what happens.
On Mon, Jul 26, 2010 at 3:18 PM, Benjamin Krajmalnik <kraj(at)servoyant(dot)com> wrote:
> 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.
>
--
To understand recursion, one must first understand recursion.
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Krajmalnik | 2010-07-26 21:47:13 | Re: upper and UTF-8 |
Previous Message | Benjamin Krajmalnik | 2010-07-26 21:18:15 | Re: upper and UTF-8 |