RE: JDBC and Unicode problem

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

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


-----Original Message-----
From: Zeljko Trogrlic [mailto:zeljko@technologist.com]
Sent: Wednesday, September 06, 2000 12:31 PM
To: pgsql-interfaces@postgresql.org
Cc: Peter Mount (Home)
Subject: RE: [INTERFACES] JDBC and Unicode problem


Which parameter? Servlet or applet don't have to know anything about
encoding.

But if you want to pass parameter from servlet/applet to driver, connection
properties would be a good place. Interbase use such approach. Interbase
example:

properties.put("user", "SYSDBA");
properties.put("password", "masterkey");
properties.put("charSet", "UTF8");
DriverManager.getConnection("jdbc:interbase://192.168.0.200/root/AIR.GDB",
properties);

At 10:01 6.9.2000 , Peter Mount wrote:
>It isn't a bug as such as I've never implemented unicode.
>
>However, your solution looks like a good one, but I'm not sure how you
would
>pass that parameter to either an applet or a servlet.
>
>There's a lot of factors here, which cause JDBC to suffer. Because of the
>sheer amount of email I see (about 200 a day each at work and at home), I
>tend to read only emails that say "JDBC" in the subject line. However, this
>means that a lot of the time I miss out on emails saying that something has
>changed (eg: getTimestamp() fails due to the format changing slightly
>between versions), and I know there's a lot of functionality in 7.0 that
>would improve things but I haven't seen enough examples to actually
>implement them...
>
>Peter