Locking Considerations
In a multi-user environment, record locking can become an issue that an application needs to handle. When one application is updating a record, that record is “locked” so that no other application can change it. This is critical in maintaining the integrity of the data.
Apache Derby supports four isolation levels: uncommitted read (UR), cursor stability (CS), read stability (RS), and repeatable read (RR). Insert, update, and delete operations always behave the same, no matter what the isolation level is. Only the behavior of SELECT statements varies depending on the isolation level.
Uncommitted Read
The uncommitted read isolation level, also known as dirty read, is the lowest level of isolation supported by Apache Derby. ...
Get Apache Derby—Off to the Races: Includes Details of IBM® Cloudscape™ now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
