Skip site navigation (1) Skip section navigation (2)

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

From: "Steve Langridge" <steve(at)vanrhynsdorp(dot)co(dot)za>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2856: Jdbc 4 connector running on JDK 1.6 should not raise exception for getClientInfo/setClientInfo
Date: 2006-12-22 08:35:55
Message-ID: 200612220835.kBM8Zts6031729@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-jdbc
The following bug has been logged online:

Bug reference:      2856
Logged by:          Steve Langridge
Email address:      steve(at)vanrhynsdorp(dot)co(dot)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.

Responses

pgsql-bugs by date

Next:From: Tomislav KarastojkovicDate: 2006-12-22 09:16:59
Subject: BUG #2857: Sequence and table partitioning
Previous:From: Gurjeet SinghDate: 2006-12-22 08:03:15
Subject: Re: BUG #2847: Bug with IN statement

pgsql-jdbc by date

Next:From: Ido M. TamirDate: 2006-12-22 10:34:03
Subject: Re: Connection pooling in java
Previous:From: janaka priyadarshanaDate: 2006-12-22 08:02:48
Subject: Connection pooling in java

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group