Re: upper and UTF-8

Поиск
Список
Период
Сортировка
От Scott Marlowe
Тема Re: upper and UTF-8
Дата
Msg-id AANLkTimgeBFoRW=xDO_aXnhjmcKhLQWWfFT43X3Deb_g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: upper and UTF-8  ("Benjamin Krajmalnik" <kraj@servoyant.com>)
Ответы Re: upper and UTF-8  ("Benjamin Krajmalnik" <kraj@servoyant.com>)
Список 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@servoyant.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.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.
>



--
To understand recursion, one must first understand recursion.

В списке pgsql-admin по дате отправления:

Предыдущее
От: "Benjamin Krajmalnik"
Дата:
Сообщение: Re: upper and UTF-8
Следующее
От: "Benjamin Krajmalnik"
Дата:
Сообщение: Re: upper and UTF-8