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.
In response to
pgsql-jdbc by date
|Next:||From: Tom Lane||Date: 2004-04-14 03:04:50|
|Subject: Re: Under what circumstances does PreparedStatement use stored plans? |
|Previous:||From: Oliver Jowett||Date: 2004-04-14 02:37:15|
|Subject: Re: patch: fix TimeTest in timezones ahead of GMT|