Message-ID: <3A239CE3.40AC0440@cres.gr>
Date: Tue, 28 Nov 2000 13:54:12 +0200
From: George Koras <gkoras@cres.gr>
MIME-Version: 1.0
To: Peter Mount <petermount@maidstone.gov.uk>
CC: fubjj@flashmail.com, pgsql-interfaces@postgresql.org
Subject: Re: How to change the encoding inside the JDBC interface
References: 
 <1B3D5E532D18D311861A00600865478CF1B5D3@exchange1.nt.maidstone.gov.uk>
Content-Type: multipart/mixed; boundary="------------CC281AFAEA0564B597E925D9"

This is a multi-part message in MIME format.
--------------CC281AFAEA0564B597E925D9
Content-Type: text/plain; charset=iso-8859-7
Content-Transfer-Encoding: 7bit

Peter Mount wrote:

> The encoding patch added a new method to Connection called getEncoding().
> The sensitive parts of Connection then replace getBytes() with
> getBytes(getEncoding()), with a new encoding argument to PG_Stream's
> ReceiveString() method.
>
> However, the encoding is only changed with the charSet connection property
> (allows you to set the encoding on a per connection basis). Now I feel this
> should default (if charSet is absent) to be the file.encoding property. What
> do you think?

It seems to be the most elegant way to do it. And yes,  a connection-specific
encoding could be useful.


--------------CC281AFAEA0564B597E925D9
Content-Type: text/x-vcard; charset=iso-8859-7; name="gkoras.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for George Koras
Content-Disposition: attachment; filename="gkoras.vcf"

begin:vcard 
n:Koras;George
x-mozilla-html:FALSE
org:Center for Renewable Energy Sources;Division for Energy Information Systems, Dissemination, and Training 
adr:;;19th km, Marathonos ave.;Pikermi;;GR-15669;Greece
version:2.1
email;internet:gkoras@cres.gr
fn:George Koras
end:vcard

--------------CC281AFAEA0564B597E925D9--