Danny, you might find the following discussion on row locking semantic helpful http://www.nabble.com/Derby-row-locking-semantic-tf3035227.html#a8434325
Mamta On 2/19/07, Danny Gallagher <[EMAIL PROTECTED]> wrote:
Question about how derby behaves: This is at the default isolation level, I am using the latest derby version, in network server mode The problem is that when one connection to the database is inserting 1000 records into a table (all in one transaction) when another connection tries to select on that table, the select is blocked until the 1000 record insert is committed. What I expected to see is that the select statement would execute without having to wait, because based on the isolation level and the select I am asking for all committed records that meet the criteria of the select statement. Why is it blocking for records that are not even committed yet? Am I missing something? Thanks ------------------------------ Find a local pizza place, movie theater, and more….then map the best route! Try it! <http://maps.live.com/?icid=wlmtag1>
