Oracle does cache lots of stuff with the statement SQL text, the key is that
you need an exact match on the SQL string to make use of it, but we should
be meeting that criteria.
At a previous employer we had a wrapper object for a Connection that
provided access to cached prepared statements by a name. We kept a hashset
of SQL strings by name and a Hashset of preparedstatement objects by name as
well. The client had to do two things, register the statement with a name
and then ask for the statement by name and the wrapper handled returning it
if it existed or creating it if not. If the wrapper ever dropped the
internal connection and recreated it then it just cleared the hashset of
preparedconnections and kept going.
We could do something similar, since Minerva can pool anything you could
have a new CachedConnection or somesuch which does something like outlined
above, or you could just modify the existing wrapper to do a little more
work on prepareStatement calls including a lookup in the cache. You could
probably add something in the config so it could be turned off/on and size
set based on something in the jcml file.
Cheers
-----Original Message-----
From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 30, 2000 9:19 AM
To: jBoss
Subject: Re: [jBoss-User] ejb-ref question
This message uses a character set that is not supported by the Internet
Service. To view the original message content, open the attached message.
If the text doesn't display correctly, save the attachment to disk, and then
open it using a viewer that can display the original character set.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
