On 2/26/07, Dag H. Wanvik <[EMAIL PROTECTED]> wrote:
"Bernt M. Johnsen" <[EMAIL PROTECTED]> writes:
> Hi,
>
>
> This behaviour is defined in the JDBC specification.
But Derby's statement cache works across connections, which alleviates
redundant statement compilation.
I ran into a connection lost exception and I had no idea why. It
wasn't obvious that this was the reason from the error given. Also,
it's not obvious why you would want to prevent sharing of prepared
statements across connections.
Amir
Please see http://db.apache.org/derby/docs/10.2/tuning/ctundepth29804.html
Dag
