From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Question about encoding combinations |
Date: | 2005-03-13 05:31:15 |
Message-ID: | 200503130531.j2D5VFZ27253@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I have updated the documentation on encodings to more closely match our
code, added descriptions, and a list of aliases for encodings. I also
reorderd the lists to they were alphabetical. Look here to see the
results:
http://candle.pha.pa.us/main/writings/pgsql/sgml/multibyte.html
Comments?
I have some questions about the second table:
Why is BIG5 listed as not allowing UTF8 on the client, but you can have
UTF8 on the server and BIG5 on the client?
Why can't you have UTF8 on the server and client?
Why can't you have MULE_INTERNAL on the server and client?
Why can't you have UTF8 on the server and SQL_ASCII on the client?
Since they all support UTF8, why can't we just allow any server/client
combination? Is the problem with unicode ordering?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2005-03-13 08:40:50 | Re: REL8_0_STABLE and 8.0.1 release client logging difference |
Previous Message | Tom Lane | 2005-03-13 04:58:40 | Re: Strange postgres planner behaviour |