client libpq multibyte support

From: SAKAIDA Masaaki <sakaida(at)psn(dot)co(dot)jp>
To: pgsql-hackers(at)PostgreSQL(dot)org
Subject: client libpq multibyte support
Date: 2000-05-05 02:43:37
Message-ID: 391235592F8.F654SAKAIDA@smtp.psn.ne.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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_server
admin=# set client_encoding='SJIS';
SET VARIABLE
admin=# \dt
List of relations
Name | Type | Owner
------------+-------+-------
SJIS_KANJI | table | admin
(1 row)

admin=# select * from SJIS_KANJI ;
\: extra argument ';' ignored
\: extra argument ';' ignored
Invalid command \. Try \? for help.

(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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike Mascari 2000-05-05 02:48:00 Re: ``..Advice For New Immigrants...
Previous Message W-A-S-P 2000-05-05 02:11:14 ``..Advice For New Immigrants...