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

Re: Statement pooling implementation (was Re: Under what circumstances does PreparedStatement use stored plans?)

From: James Robinson <jlrobins(at)socialserve(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Statement pooling implementation (was Re: Under what circumstances does PreparedStatement use stored plans?)
Date: 2004-04-14 02:39:12
Message-ID: E9A8CFA3-8DBC-11D8-8D1B-000A9566A412@socialserve.com (view raw or flat)
Thread:
Lists: 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


In response to

pgsql-jdbc by date

Next:From: Tom LaneDate: 2004-04-14 03:04:50
Subject: Re: Under what circumstances does PreparedStatement use stored plans?
Previous:From: Oliver JowettDate: 2004-04-14 02:37:15
Subject: Re: patch: fix TimeTest in timezones ahead of GMT

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