From: "Mike Cannon-Brookes" <mcannon@internet.com>
To: <pgsql-interfaces@postgresql.org>
Subject: RE: JDBC and Unicode problem 
Date: Tue, 14 Nov 2000 23:42:33 +1100
Message-ID: <NCBBKLKCHGCKLBAFEDFDOELPHAAA.mcannon@internet.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal

Guys,

Did these changes get worked into the latest driver src?

I looked at the changes file at
http://www.retep.org.uk/postgres/changelog.html but the only possible change
I see after the date of this email is:
- Merged in some last patches. Only 1 left, which may not be compatible with
jdbc1

I'm trying to convert a current site from HSQL (eugh!) to PostgreSQL but I
can't get the Unicode working as per this email thread - I've tried the
usual compile with Unicode, createdb with unicode encoding etc.


Many thanks,
Mike


>Thanks. I checked code and the idea seems fine. I hope it will fine the way
>to regular JDBC driver soon. It similar to idea I sent few days ago - all
>great minds thinks similar :)

>BTW is there anonymous CVS account on PostgreSQL repository?

>At 09:13 11.9.2000 , Tatsuo Ishii wrote:
>>MOTOKI Sinichi, a subscriver of our PostgreSQL local mailing list, has
>>made a patch for 7.0.2 JDBC driver. With the patch and MB enabled
>>installation (configure --enable-multibyte=UNICODE), you could use
>>UTF-8 acording to him. You will need to create db with -E UNICODE if
>>you did just --enable-multibyte (witout =UNICODE), or you choose other
>>encodings.
>>--
>>Tatsuo Ishii
>>
>>> I was thinking of parameter's to the JVM on startup (like
>>> -Djdbc.driver=org.postgresql.Driver )
>>>
>>> As for connection properties, yes they are an ideal place, and back in
the
>>> 6.3 days we used to use them so the mechanism is in there. I think the
>>> connection properties is the way to go, as it would then work
everywhere.
>>>
>>> Peter
>>
>>