From: | "Linder Poclaba" <linder(dot)poclaba(at)gmail(dot)com> |
---|---|
To: | "Linder Poclaba" <linder(dot)poclaba(at)gmail(dot)com>, "Felipe Amezquita" <felmarla(at)gmail(dot)com>, postgresayuda <pgsql-es-ayuda(at)postgresql(dot)org> |
Subject: | Re: Cambiar Encoding de mi BD |
Date: | 2006-08-19 23:00:16 |
Message-ID: | 5aa69e1b0608191600j6af0b2c2xb9f25796b2f6c9d6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda |
2006/8/19, Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
>
> Linder Poclaba escribió:
>
> > Entonces lo que dices no está documentado, volvía a leer la
> documentación y
> > dice que se puede tener multiples bases de datos cada una con diferentes
> > conjunto de caracteres, gracias por el dato :)
>
> http://www.postgresql.org/docs/8.1/static/multibyte.html
>
> 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.
ok gracias Alvaro.
--
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
--
Linder Poclaba Lázaro.
Desarrollador Key Optimal Solutions KEYOS.
Usa Software Libre y obtiene tú libertad.
From | Date | Subject | |
---|---|---|---|
Next Message | Gregorio Diaz | 2006-08-19 23:07:44 | Re: Conexiones externas a V 8.1 en windows |
Previous Message | Alvaro Herrera | 2006-08-19 22:54:16 | Re: Cambiar Encoding de mi BD |