thanks Oystein and Mike for replying. Changing the question slightly, with Oracle under the same circumstances session 2 can see the committed data (default isolation level is read committed). The developers want to see the same in derby, is that possible?
Øystein Grøvlen wrote On 11/24/05 05:43,: > You might get a table lock when scanning the whole table (as a select > without a predicate will do). However, this query would not succeed > even if row locking was used, since the scan would be blocked by the > lock on (c,d). > > Except when using 'read uncommitted' isolation level, a query will be > blocked when it encounters a row with uncommitted changes. >
