From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Alejandro Gasca <agasca(at)yahoo(dot)com> |
Cc: | Hensa <hensa22(at)yahoo(dot)es>, pgsql-es-ayuda(at)postgresql(dot)org |
Subject: | Re: Upper y Lower |
Date: | 2006-12-19 13:32:28 |
Message-ID: | 20061219133228.GB27098@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda |
Alejandro Gasca escribió:
> initdb -E=UTF8 --locale=es_MX -D=ruta
El unico defecto es que con esto corres el riesgo de que los
ordenamientos sean incorrectos. Aca lo que has hecho es definir una
combinacion de locale y encoding que no son compatibles.
Dice el manual
Important: Although you can specify any encoding you want for a
database, it is unwise to choose an encoding that is not what is
expected by the locale you have selected. The LC_COLLATE and
LC_CTYPE settings imply a particular encoding, and
locale-dependent operations (such as sorting) are likely to
misinterpret data that is in an incompatible encoding.
Since these locale settings are frozen by initdb, the apparent
flexibility to use different encodings in different databases of
a cluster is more theoretical than real. It is likely that these
mechanisms will be revisited in future versions of PostgreSQL.
http://www.postgresql.org/docs/8.2/static/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Diaz | 2006-12-19 13:34:16 | Removiendotablas temporales |
Previous Message | Alvaro Herrera | 2006-12-19 13:28:48 | Re: Upper y Lower |