From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | "Mike C(dot)" <mcbp223(at)yahoo(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [BUGS] BUG #2856: Jdbc 4 connector running on JDK 1.6 should |
Date: | 2007-10-07 19:48:53 |
Message-ID: | Pine.BSO.4.64.0710071543340.31469@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 28 Sep 2007, Mike C. wrote:
> On Fri, 5 Jan 2007, Steve Langridge wrote:
>
>> At the present time, I am not really interested in actually using the client
>> info data at all - I really just need the getClientInfo() and setClientInfo()
>> to rather not raise a not-implemented exception. With the JDBC 3 driver
>> under Java 1.5, there were no problems, so I presume these methods were
>> implemented - it is now a real hassle since when running under Java 1.6, one
>> has to use the JDBC 4 driver.
>>
>
> This is getting old, would you accept the naive implementation and
> leave the bug open until someone implements the real logic? It's really
> a showstopper on Glassfish / JDK 1.6
>
I've implemented this in a similar fashion. The Javadoc spec indicates
that setting a clientinfo property that isn't supported is an error, so
I've done that. So now it won't throw an error on getClientInfo or
setClientInfo with a null or empty properties. Can you test this jar file
and see if it works for you?
http://ejurka.com/pgsql/jars/clientinfo/
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2007-10-07 22:47:24 | Re: PreparedStatement rounds doubles to scale 14 during update |
Previous Message | Till Toenges | 2007-10-06 12:48:43 | Re: statement caching link on jdbc page |