From: | Carlos Alberto Silva <casxxi(at)yahoo(dot)com(dot)ar> |
---|---|
To: | pgsql-es-ayuda(at)postgresql(dot)org |
Subject: | Re: SOT: Mensaje de PostgreSQL |
Date: | 2009-11-11 00:10:48 |
Message-ID: | 4AFA0108.4060701@yahoo.com.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda |
ReynierPM escribió:
> Buenos días a todos:
> Quizás esto sea una pregunta tonta pero me ataca la curiosidad. ¿Qué
> significa? ¿Qué implicaciones me puede traer en mi BD?
>
> Database encoding
> The database bacula_db is created to store data using the SQL_ASCII
> encoding. This encoding is defined for 7 bit characters only; the
> meaning of characters with the 8th bit set (non-ASCII characters
> 127-255) is not defined. Consequently, it is not possible for the
> server to convert the data to other encodings.
> If you're storing non-ASCII data in the database, you're strongly
> encouraged to use a proper database encoding representing your locale
> character set to take benefit from the automatic conversion to
> different client encodings when needed. If you store non-ASCII data in
> an SQL_ASCII database, you may encounter weird characters written to
> or read from the database, caused by code conversion problems. This
> may cause you a lot of headache when accessing the database using
> different client programs and drivers.
> For most installations, Unicode (UTF8) encoding will provide the most
> flexible capabilities.
pero ... yo tengo hace años varias bases en SQL_ASCII y tengo acentos y
eñes ...
cas
From | Date | Subject | |
---|---|---|---|
Next Message | Edwin Quijada | 2009-11-11 00:15:05 | RE: Problema con shared buffers and SHMMAX |
Previous Message | Edwin Quijada | 2009-11-11 00:00:17 | RE: Tareas a realizar sobre un servidor PostgreSQL |