RE: RE: JDBC and Unicode problem

See below:

--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount(at)maidstone(dot)gov(dot)uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council

-----Original Message-----
From: Mike Cannon-Brookes [mailto:mcannon(at)internet(dot)com]
Sent: Wednesday, November 15, 2000 6:56 AM
To: Peter Mount; pgsql-interfaces(at)postgresql(dot)org
Subject: RE: [INTERFACES] RE: JDBC and Unicode problem

I'm using a driver built from the 7.0.3 source downloaded as of 24 hours
ago.

I still get ???'s in the database when using a UNICODE encoded DB and having
compiled the server with --enable-multibyte=UNICODE .

What's the best way to test whether the problem is in the driver?

PM: If I get chance I'll try to build a backend with multibyte enabled.

Can anyone think of another place to look for problems? (Bearing in mind
this setup works fine with HSQL which uses Unicode natively)

This is using EJBs so JDBC 2 is required, could it be the arrays problem?

PM: No, as you would be getting "not implemented" exceptions...

Thanks for any assistance - deadlines are rushing up fast ;)

Mike

> -----Original Message-----
> From: pgsql-interfaces-owner(at)postgresql(dot)org
> [mailto:pgsql-interfaces-owner(at)postgresql(dot)org]On Behalf Of Peter Mount
> Sent: Wednesday, November 15, 2000 12:00 AM
> To: 'Mike Cannon-Brookes'; pgsql-interfaces(at)postgresql(dot)org
> Subject: RE: [INTERFACES] RE: JDBC and Unicode problem
>
>
> The current sources in cvs should work with unicode. One of the other
> patches that did get in dealt with making the driver handle
> string encodings
> correctly.
>
> If you still have problems let me know.
>
> PS: The patch I've not applied yet deals with handling Arrays (part of the
> JDBC2 spec), however I'm not sure how that patch works fully, and as it
> patches org.postgresql.Connection it could affect how jdbc1 works, hence
> that comment in changelog.
>
> Peter
>
> --
> Peter Mount
> Enterprise Support Officer, Maidstone Borough Council
> Email: petermount(at)maidstone(dot)gov(dot)uk
> WWW: http://www.maidstone.gov.uk
> All views expressed within this email are not the views of
> Maidstone Borough
> Council
>
>
> -----Original Message-----
> From: Mike Cannon-Brookes [mailto:mcannon(at)internet(dot)com]
> Sent: Tuesday, November 14, 2000 12:43 PM
> To: pgsql-interfaces(at)postgresql(dot)org
> Subject: [INTERFACES] RE: JDBC and Unicode problem
>
>
> 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
> >>
> >>
>