Skip site navigation (1) Skip section navigation (2)

RE: [INTERFACES] JDBC: Default encoding problem

From: Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>
To: "'Bartek Teodorczyk'" <barteo(at)it(dot)pl>, pgsql-interfaces(at)postgresql(dot)org
Cc: "Peter Mount (Home)" <peter(at)retep(dot)org(dot)uk>
Subject: RE: [INTERFACES] JDBC: Default encoding problem
Date: 1999-10-14 12:23:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
It would be a bad idea to modify PG_Stream, as this will affect the
LargeObject support which must be kept binary.

Also, what version of the driver are you using, as there has been a lot
of changes recently.


Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.

-----Original Message-----
From: Bartek Teodorczyk [mailto:barteo(at)it(dot)pl]
Sent: 14 October 1999 11:35
To: pgsql-interfaces(at)postgreSQL(dot)org
Subject: [INTERFACES] JDBC: Default encoding problem

I've noticed crossplatform problem using encoding in JDBC interface.
I want to use ISO8859-2 characters in my database and accessing from
java interface in Windows and Linux.
Default encoding in Linux is - ISO8859-2 but in Windows CP1250 and
during transmission via Input/OutputStream some localized characters are
truncated to '?'.

I've hacked a little JDBC inteface and my proposition is to change in
1. use InputStreamReader except InputStream
2. use BufferedWriter except BufferedOutputStream



pgsql-interfaces by date

Next:From: Rajive P. SoodDate: 1999-10-14 12:58:31
Subject: Inquiry
Previous:From: Patrick WelcheDate: 1999-10-14 11:36:07
Subject: Re: [INTERFACES] ODBC / M$Access error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group