db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gregsmit <gregs...@us.ibm.com>
Subject Re: Memory Leak or Expected Behavior - BtreePostCommit
Date Tue, 30 Oct 2007 14:42:51 GMT

Hi Mike,

The default isolation settings are being used.  The data framework we are in
does allows the application to change the isolation level, but does not by
default.  Our application does not change the default, so Derby's embedded
defaults should be the ones that are in use here.


Mike Matrigali wrote:
> I meant the SQL isolation level.  Derby's default isolation level is 
> read committed, but can be changed by either the application or possibly
> the framework you are running in.

View this message in context: http://www.nabble.com/Memory-Leak-or-Expected-Behavior---BtreePostCommit-tf4712054.html#a13490071
Sent from the Apache Derby Users mailing list archive at Nabble.com.

View raw message