-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Also note that derby has a per database statement cache. Statements from any connection can share the same statement execution plan, avoiding compilation by using the statement cache. But it does not maintain them across reboots. When an application submits an SQL stmt that exactly matches the one already in the cache, it grabs the statement from the cache. This doc talks about the statement cache: http://incubator.apache.org/derby/manuals/tuning/perf34.html#IDX440
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBUcLdEpeslyHqPs0RAlVUAJ4rdtB3dzU67Y0M7znCDBrO5jw5pgCeL6qG JaAozg1nVRmFpBDNHSuEpy4= =CHKZ -----END PGP SIGNATURE-----
