From: | Ivo Danihelka <ivo(dot)danihelka(at)itonis(dot)tv> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | UTF8 should be accepted as UNICODE |
Date: | 2008-02-22 14:08:14 |
Message-ID: | 1203689294.4960.56.camel@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
The Postgresql JDBC driver does not accept this statement:
SET client_encoding = 'UTF8';
It fails with:
"org.postgresql.util.PSQLException: The server's client_encoding
parameter was changed to UTF8. The JDBC driver requires client_encoding
to be UNICODE for correct operation."
I consider that to be a bug. The UNICODE is an alias for UTF8.
Starting from 8.2, the pg_dump exports 'UTF8'
even when --encoding=UNICODE is used.
See:
$ pg_dump --version
pg_dump (PostgreSQL) 8.2.6
$ pg_dump --encoding=UNICODE template1 | grep client_encoding
SET client_encoding = 'UTF8';
The check for value.equals('UNICODE') is inside
org/postgresql/core/v3/QueryExecutorImpl.java
Thanks for the driver,
--
Ivo Danihelka
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2008-02-22 14:21:03 | Re: UTF8 should be accepted as UNICODE |
Previous Message | Oliver Jowett | 2008-02-22 11:46:50 | Re: Problem executing remote SELECT's (through internet) with JDBC |