| From: | ReynierPM <rperezm(at)uci(dot)cu> |
|---|---|
| To: | pgsql-es-ayuda(at)postgresql(dot)org |
| Subject: | SOT: Mensaje de PostgreSQL |
| Date: | 2009-11-10 14:57:31 |
| Message-ID: | 4AF97F5B.2040106@uci.cu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-es-ayuda |
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.
--
Saludos
ReynierPM
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-11-10 15:06:44 | Re: [pgsql-es-fomento] PGDay.eu, Paris: it was awesome! |
| Previous Message | Francisco Javier Morosini Eguren | 2009-11-10 14:52:41 | PGDay.eu, Paris: it was awesome! |