My understanding is that the Derby prepared statement cache is portable
across connections. It is usable by any connection to the same database
-- the prepared statement text is compared with existing cached
statements and if it alreday exists then it is reused.
But it's not my area of expertise; there are others who can confirm or
deny what I say here.
David
Daniel Morton wrote:
Over the past few threads, someone mentioned that the
PreparedStatements are cached on the database even
when the connection that created the
PreparedStatements are closd... I was discussing that
very issue with an associate of mine a couple of weeks
ago, and he assured me that the Oracle and DB2 people
he knew told him that the PreparedStatements did not
persist between connections. Is that incorrect, or
does Derby just handle it differently?
Thanks,
djm
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
