Re: Character encoding problem - Mailing list pgsql-jdbc

From Boris Klug
Subject Re: Character encoding problem
Date
Msg-id 200302141048.55708.boris.klug@control.de
Whole thread Raw
In response to Re: Character encoding problem  (Barry Lind <blind@xythos.com>)
List pgsql-jdbc
Hello!

> > OK, so I created the db using "initdb -E LATIN1" which does not helped.
> > Using "initdb -E UNICODE" will give even more problems: I wasnt able to
> > insert umlauts using psql...

OK, I retested the whole stuff, here a quick summay:

1) Using "initdb -E LATIN1" when creating a database.

Works great, that was the trick: I can now use pg73b1jdbc2, pg73rc1jdbc2 or
pg73jdbc2.


2) Using "initdb" (leads to encoding "SQL_ASCII":

I can retrieve umlauts when I use use the pg73b1jdbc2 driver with the option
"charSet=ISO_8859_1" in the JDBC connection url. That is what we used till
now - I think we have to switch to LATIN1 enconding when we migrate to 7.3.1
(from 7.2).

I was using PostgreSQL 7.3.1, running on Linux with JDK 1.4.

--
Dipl. Inform. Boris Klug, control IT GmbH, Germany

pgsql-jdbc by date:

Previous
From: "Carl Olivier"
Date:
Subject: Database Instance creation
Next
From: Rafal Kedziorski
Date:
Subject: JDBC vs. Entity Bean with JBoss