| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Encoding holes |
| Date: | 2001-09-23 08:45:33 |
| Message-ID: | 4.2.0.58.20010923101546.00a79bd0@pop.freesurf.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
http://www.postgresql.org/idocs/index.php?app-psql.html
In psql \l (or \list) [...]. If your Postgres installation was compiled
with multibyte encoding support, the encoding scheme of each database is
shown as well.
****
To support UNICODE, PostgreSQL needs to be compiled with the right options.
Currently, in 7.1, there is no way to know which encodings are available
server-side.
****
Another info : there are holes between numbers:
12, 13, 14 and 15 return nothing. But:
16 -> KOI8
17 -> WIN
18 -> ALT
etc ...
Cheers,
Jean-Michel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Michel POURE | 2001-09-23 09:28:13 | Transform pgSchema into a Multi-database wrapper |
| Previous Message | Dave Page | 2001-09-23 07:25:23 | Re: Database encoding |