Jonathan Carlson <[EMAIL PROTECTED]> writes:
> Has anyone else found similar results? If the performance improvement
> is anywhere close to the same on other databases too (this test was
> done with DB2), then I would bet that Torque has a PreparedStatement
> caching mechanism along with its db connection caching mechanism. Is
> that true? Or maybe it is impossible to reuse a PreparedStatement
> across transaction boundaries, which would eliminate any hopes of
> caching them. ????
PreparedStatement objects are associated with the Connection object
used to create them. When using a connection pool (as Turbine does),
you never know which connection you're going to be using for the
execution of a given SQL statement. It would be possible to have a
Statement cache for pooled connection.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
