| From: | pgsql-bugs(at)postgresql(dot)org |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | PostgreSQL 7.1+ screw up Chinese Encoding after JDBC |
| Date: | 2001-05-16 15:33:46 |
| Message-ID: | 200105161533.f4GFXkN55130@hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jeff Liu (liu(at)WonderfulSolutions(dot)com) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
PostgreSQL 7.1+ screw up Chinese Encoding after JDBC
Long Description
I can read Chinese Encoding (gb2312) using select statement manually
in psql after I installed PostgreSQL 7.1 or 7.1.1. However, my JDBC
select statement returns incorrect Chinese Encoding (screw up the
whole Chinese encoding). I did recompile postgresql.jar (JDBC driver)
for my new version of PostgreSQL. I have to go back to my old version
of PostgreSQL (7.0.3) to have correct Chinese Encoding. Very sad!
Configuration I have:
Redhat 6.1 + Linux 2.4.2 kernel (I did recompile the kernel)
Java: IBM JDK 1.3.0
gcc: version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
PostgreSQL: recompile 7.1 and 7.1.1 with --enable-multibyte and --with-java options.
Sample Code
No file was uploaded with this report
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-05-16 15:39:09 | Re: REQ: build src/backend/postgres w/o -lncurses or -lreadline |
| Previous Message | pgsql-bugs | 2001-05-16 15:20:05 | Loss of avg() functionality |