I understand that. However, the other JDBC drivers we use don't have
such an issue. Their connection pool might remember the statement's
owner thread or something excessive like that.
Anyway, it's not about close()s on Connection, just on Statement or
And moreover, implementation issues should not affect interface.
DC> You are absolutely correct this should not happen. You do however
DC> realize that close on a PooledConnection returns it to the pool?
>> As JDK java.sql.Statement.close() documentation specifies, calling
>> Statement.close() on already close()d statement should have no effect.
>> It's the way Oracle and MS SQL drivers behave, but PG driver throws
>> this exception.
>> Thank you.
Thank you and thank Kris.
In response to
pgsql-jdbc by date
|Next:||From: Pablo Velasquez Rivas||Date: 2004-02-24 14:19:36|
|Subject: Losing Connections|
|Previous:||From: Pablo Velasquez Rivas||Date: 2004-02-24 13:42:25|
|Subject: Re: Postgres and JBuilderX on Linux|