db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendleton.de...@gmail.com>
Subject Re: Cannot read table while writing transaction in another connection
Date Tue, 31 Jul 2012 00:27:01 GMT
> I would have expected that around line 175 I would get the row count
> as it was before the uncommitted
> transaction started and that no lock would be needed to just read.

Unfortunately, Derby doesn't currently implement these "snapshot isolation"
types of semantics.

> Is this the way it is supposed to work? If so, is there some
> configuration parameters that I can set up
> to get the behavior I expected?

You can try using a lower isolation level:

But that's not exactly the same thing (e.g., at a lower isolation level,
it might be that the count returns the instantaneous count of rows
in the table, including some rows from uncommitted transactions).



View raw message