client libpq multibyte support
От | SAKAIDA Masaaki |
---|---|
Тема | client libpq multibyte support |
Дата | |
Msg-id | 391235592F8.F654SAKAIDA@smtp.psn.ne.jp обсуждение исходный текст |
Ответы |
Re: client libpq multibyte support
|
Список | pgsql-hackers |
Hi, A client application using libpq made by non-MULTIBYTE can not talk to server made by MULTIBYTE. (Example) ------------------------------------------------------------A_server(non-MULTIBYTE) B_server(--enable-multibyte=EUC_JP) | | --+----------+----------+-- network | C_server(non-MULTIBYTE) By using the C_server's psql(+non-MULTIBYTE-libpq),prompt> psql -h B_serveradmin=# set client_encoding='SJIS';SET VARIABLEadmin=#\dt List of relations Name | Type | Owner ------------+-------+-------SJIS_KANJI | table | admin (1 row) admin=# select * from SJIS_KANJI ;\: extra argument ';' ignored\: extra argument ';' ignoredInvalid command \. Try \? forhelp. (Here, "SJIS_KANJI" is SJIS multibyte code.) ----------------------------------------------------------- Is this a specification ? I hope that a client 7.0-libpq and an application always be made by "configure --enable-multibyte" even if MULTIBYTE isn't necessary for backend. If so, the above problem will be solved. -- Regard, SAKAIDA Masaaki -- Osaka, Japan
В списке pgsql-hackers по дате отправления: