On Tue, 10 Dec 2002, Mike Beachy wrote:
> p.s. I think I see what you mean now - createStatement() gets added to
> ConnectionHandler as one of the intercepted methods; it calls
> createStatement() on the real Connection, but wraps the result in a
> Statement proxy that intercepts calls to getConnection and returns the
> Connection proxy instead of the actual Connection?
Exactly so.
I've attached context diffs for
org.postgresql.test.jdbc2.optional.ConnectionPoolTest and
org.postgresql.jdbc2.optional.PooledConnectionImpl.
The updated test does what Mike suggested, for Statements,
PreparedStatements, and CallableStatements. The updated PooledConnection
adds a statement proxy as described above.
Aaron
P.S. When I run the test suite against my 7.2.2 server with the JDBC3
driver, I get a failure in DatabaseMetaData.testTables. It is returning
the name of the first table in the database, so the table name criterion
doesn't seem to be working:
testTables(org.postgresql.test.jdbc2.DatabaseMetaDataTest)
junit.framework.AssertionFailedError at
org.postgresql.test.jdbc2.DatabaseMetaDataTest.testTables(DatabaseMetaDataTest.java:56)
