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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
