Ahhh.... I just misunderstood your point entirely. Sure, we
could have every Connection cache it's PreparedStatements. Again, I don't
think that will be a major gain, but it'll take about 2 seconds so I can
go ahead and put it in.
Aaron
On Wed, 30 Aug 2000, Rickard [iso-8859-1] �berg wrote:
> Hm.. I don't follow you here. Cached PreparedStatements are per
> Connection, so every connection will have a set of prepared statements,
> hence no need to do trickery as you outline above.
>
> Here's what I propose: in your connection wrapper, on prepareStatement
> you simply check a cache against the SQL. If it's there, return it,
> otherwise create a new prepared statement, put it in cache, and return
> it. Very very simple.
>
> Seems ok? Or am I missing something here...
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
