Re: BUG #2856: Jdbc 4 connector running on JDK 1.6 should

From: Kris Jurka <books(at)ejurka(dot)com>
To: Steve Langridge <steve(at)vanrhynsdorp(dot)co(dot)za>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: BUG #2856: Jdbc 4 connector running on JDK 1.6 should
Date: 2007-01-05 17:25:51
Message-ID: Pine.BSO.4.64.0701051220030.12450@leary2.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

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.
>

These methods are new in JDBC 4 which is why it wasn't a problem with JDBC
3. I understand that all you want is not to error, but I don't think
that's appropriate behavior for all users.

Kris Jurka

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jonathan Hull 2007-01-07 22:46:49 BUG #2873: Function that returns an empty set with a 'not null' domain errors in 8.2 but not 8.1
Previous Message Kris Jurka 2007-01-04 16:37:31 Re: BUG #2856: Jdbc 4 connector running on JDK 1.6 should

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2007-01-05 17:32:10 Re: issues with Statement.getTimestamp(int, Calendar)
Previous Message Kris Jurka 2007-01-05 17:17:55 Re: help with front/backend datatype converting