Re: Statement pooling implementation (was Re: Under what circumstances does PreparedStatement use stored plans?) - Mailing list pgsql-jdbc

From James Robinson
Subject Re: Statement pooling implementation (was Re: Under what circumstances does PreparedStatement use stored plans?)
Date
Msg-id E9A8CFA3-8DBC-11D8-8D1B-000A9566A412@socialserve.com
Whole thread Raw
In response to Statement pooling implementation (was Re: Under what circumstances does PreparedStatement use stored plans?)  (Oliver Jowett <oliver@opencloud.com>)
List pgsql-jdbc
On Apr 13, 2004, at 10:22 PM, Oliver Jowett wrote:

> I'd leave the core driver alone and look at implementing the pooling
> in the ConnectionPoolDataSource layer. There are already proxy
> Connection and Statement objects created by PooledConnectionImpl; you
> should be able to intercept Connection.prepareStatement() and
> Statement.close() to manage the statement pool. The pool itself ends
> up attached to a PooledConnectionImpl.

Sounds more than reasonable. Overriding close() in
AbstractJdbc3Statement to perform "less" if it was pooled was looking
ugly at best.


----
James Robinson
Socialserve.com


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: patch: fix TimeTest in timezones ahead of GMT
Next
From: Tom Lane
Date:
Subject: Re: Under what circumstances does PreparedStatement use stored plans?