Re: Encoding problem
От | danny |
---|---|
Тема | Re: Encoding problem |
Дата | |
Msg-id | 005201c0b218$5d2e2b80$f100a8c0@japan.autotools.net обсуждение исходный текст |
Ответ на | Encoding problem (pgsql-bugs@postgresql.org) |
Ответы |
Re: Encoding problem
|
Список | pgsql-bugs |
Dear Sir : Thanx. After tried it again, it still couldn't work now. The result is the same error. ********************************************* template1=# \encoding EUC_TW template1=# \z Access permissions for database "template1" Relation | Access permissions ----------+-------------------- (0 rows) template1=# create table a( a text); CREATE template1=# insert into a values('許å¤'); INSERT 18761 1 template1=# select * from a; a ----- éµh (1 row) template1=# insert into a values('許\å¤'); INSERT 18762 1 template1=# select * from a; a ------ éµh è¨±å¤ (2 rows) ********************************************* It seems it ate the "\" , so the word it appeared not the origin one. Danny ----- Original Message ----- From: "Tatsuo Ishii" <t-ishii@sra.co.jp> To: <danny.kao@autotools.com.tw>; <pgsql-bugs@postgresql.org> Sent: Wednesday, March 21, 2001 10:14 PM Subject: Re: [BUGS] Encoding problem > Danny Kao (danny.kao@autotools.com.tw) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > Encoding problem > > Long Description > I have tried "initdb --encoding=BIG5" You cannot do that (documented in README.mb). If you want to use traditional chinese do: initdb --encoding=EUC_TW instead. -- Tatsuo Ishii
В списке pgsql-bugs по дате отправления: