dbTalk Databases Forums  

[BUGS] BUG #2856: Jdbc 4 connector running on JDK 1.6 should not raise exception for getClientInfo/setClientInfo

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] BUG #2856: Jdbc 4 connector running on JDK 1.6 should not raise exception for getClientInfo/setClientInfo in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Steve Langridge
 
Posts: n/a

Default [BUGS] BUG #2856: Jdbc 4 connector running on JDK 1.6 should not raise exception for getClientInfo/setClientInfo - 12-25-2006 , 10:38 AM







The following bug has been logged online:

Bug reference: 2856
Logged by: Steve Langridge
Email address: steve (AT) vanrhynsdorp (DOT) co.za
PostgreSQL version: 8.2
Operating system: Windows XP Pro SP2
Description: Jdbc 4 connector running on JDK 1.6 should not raise
exception for getClientInfo/setClientInfo
Details:

When using the Jdbc 4 driver running on Java 1.6, it would be preferable if
the methods getClientInfo() and setClientInfo() returned silently, instead
of raising an exception about not being implemented. When running on
Glassfish with Toplink Essentials, the app server log gets filled with these
exceptions for every access from a JDBC connection pool (when using the
PGConnectionPoolDataSource).

This has been discussed on the Nabble forums, but I do not see that it has
been posted anywhere on the Postgres forums.

Regards,

Steve.

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

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.