Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese - Mailing list pgsql-bugs

From Gordon Luk
Subject Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese
Date
Msg-id 3D1AC770.4010004@gforce.ods.org
Whole thread Raw
In response to [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese (Big5)!!! Version 7.2.1 (come with Redhat 7.3)]  (Gordon Luk <gordon@gforce.ods.org>)
List pgsql-bugs
Tatsuo Ishii wrote:

>>Ok, but problem is, when i try encode with unicode, it also reject
>>me.... invalid UNICODE charater.... :-(
>>
>>
>
>Show me the entire error message please.
>

Ok... error like this...
ERROR : Invalid UNICODE character sequence found (0xe5a672)...

the input charater also "¤¤¤å¦r"....

>Actually PostgreSQL does support Big5. To use Big5, set the client
>encoding to Big5 and set the server(DB) encoding to EUC_TW. PostgreSQL
>will take care of the conversion between Big5 and EUC_TW.
>
>There are several ways to set the client encoding to Big5:
>
>SQL: set client_encoding to 'Big5';
>from psql: \encoding Big5
>using environment variable: export PGCLIENTENCODING=Big5 (example for bash)
>
>Hope this helps,
>--
>Tatsuo Ishii
>
>
O... you are right, i use Pgadmin II , and type SQL by hand ... and add
the "set client_encoding to 'Big5';" before insert statement.... It
WORK!!!! Thanks...


Gordon

pgsql-bugs by date:

Previous
From: Gordon Luk
Date:
Subject: Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese
Next
From: Tom Lane
Date:
Subject: Re: weird strncmp bug while executing trigger?