Re: Encoding

From: "Ryan Chambers" <ryan(at)squaretrade(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Encoding
Date: 2002-05-09 16:47:07
Message-ID: NEBBICFOPMHJEAGDAAIHCEFDDMAA.ryan@squaretrade.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc


I've had problems like this too, but it was an OS issue. Basically, the
default character set for Solaris is ASCII, but our data was all ISO-8859-1.
This was causing the ? corruptions that you mention.

This was solved by adding the following commands to the shell script I use
to run the java application:

LC_CTYPE=iso_8859_1

export LC_CTYPE

I don't know if this can be of any use to you, though. Good luck.

Ryan

-----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Thomas De Vos
Sent: Wednesday, May 08, 2002 9:49 AM
To: ThomasDeVos(at)it-enterprise(dot)co(dot)uk; pgsql-jdbc-owner(at)postgresql(dot)org
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] Encoding

Hiya,

The problem seems to be solved. Added debugging information in the
Postgres Driver and at the end after several tests I was able to conclude
that it didn't has anything to do with the driver.
So I wrote a few sample apps. (reading - writing from file with extended
character set in it) and it was the BlackDown JVM who behaves very strange
and also the Sun's JVM seems to behave very strange and translate (converts)
these characters into "?".
Only the IBM's JVM seems to work fine.

The OS is Debian Linux with Blackdown JVM who gave me a few nights without
rest!!!!

Thomas De Vos

[Thomas De Vos] -----Original Message-----
From: pgsql-jdbc-owner(at)postgresql(dot)org
[mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Thomas De Vos
Sent: 06 May 2002 20:58
To: pgsql-jdbc-owner(at)postgresql(dot)org
Cc: pgsql-jdbc(at)postgresql(dot)org; ThomasDeVos(at)it-enterprise(dot)co(dot)uk
Subject: [JDBC] Encoding

Hiya,

I was 2 months ago using the sourceforge JDBC driver on WinNt as client
and HP-UX as server (so PostgresQl) server. At time I had problems with the
extented ASII set, all the characters were converted to "?". So I switched
to the org.postgresql.Driver and problem seems to be solved.
Now 2 months later we have to go into production and the target OS is
Debian Linux for client and server. And guess what I can see the same
problem, all characters belonging to the extented set are converted to "?".

I have written a small testprogram, create one connection and tries to
insert data with Java and JDBC. This seems not to work. But .... if I insert
data with psql -h ... -f insertcommandfile.sql and look then in the database
then there is no problem at all. Extented Characters are inserted. So I
suppose the Db is correctly configured. (eg client-encoding and server
encoding).
I have seen that ages ago the JDBC driver had problems with encoding but
this was solved I thought.
I'm testing with this character: é, but also other characters has the
same problem.

I need help .... Real help ...

Kind regards,

Thomas De Vos
IT Enterprise Ltd
Phone: 00 44 (0)127 650 5385
Mobile: 00 44 (0)777 990 7717
ThomasDeVos(at)it-enterprise(dot)co(dot)uk

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Marin Dimitrov 2002-05-09 17:01:23 Re: extended error codes in the JDBC driver
Previous Message Barry Lind 2002-05-09 15:42:45 Re: extended error codes in the JDBC driver