From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Eric Tan <neltan2002(at)yahoo(dot)com(dot)hk> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: How to insert Chinese (big5) through JDBC? |
Date: | 2003-07-30 11:42:55 |
Message-ID: | Pine.LNX.4.33.0307300741300.1742-100000@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Wed, 30 Jul 2003, [big5] Eric Tan wrote:
> Hi all,
> I encounter problem when inserting Chinese.
> These are my setting:
> - postgresql 7.3 (database encoding: "SQL_ASCII")
> - JDBC: pg73jdbc2.jar
> - Tomcat 4.1.24
> - JSP/Servlet/Java Bean
> insert into table1 values('¤@¤G¤T') // chinese cannot display here...
> Insert Chinese words are ok. But when I select the record, there were wrong sth. like '? ?³æ '
> The sql statement is in big5 format because I write it in a log file.
> I've tried using charset like this. Not knowing why. All fail...
> jdbc:postgresql://202.71.201.252:5432/CA_care?charSet=ISO-8859-1
> jdbc:postgresql://202.71.201.252:5432/CA_care?charSet=SQL_ASCII
> jdbc:postgresql://202.71.201.252:5432/CA_care?charSet=UTF-8
> jdbc:postgresql://202.71.201.252:5432/CA_care?charSet=Big5
>
> Any idea.
> Best Regards,
> Eric Tan
You cannot store Big5 data in a SQL_ASCII encoded database. Consider
using UNICODE. Also the ?charset=xxx argument in the database URL is no
longer valid in the Postgresql JDBC drivers starting with 7.3.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-07-30 13:48:54 | Re: Very strange 'now' behaviour in nested triggers. |
Previous Message | Peter Eisentraut | 2003-07-30 07:54:20 | Re: [HACKERS] Passing server_encoding to the client is not future-proof |