[CAUSEWAY-2154] Remove support for persistent object concurrency checking

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Resolved
• Fix Version/s: 2.0.0-M3
• Assignee: Andi Huber
• Reporter: Andi Huber
• Created: 18/Jul/19 07:01
• Updated: 18/Jul/19 09:45
• Resolved: 18/Jul/19 09:39

Description

Concurrency Checking:

The OID contains the version/timestamp of the object as retrieved from the DB.So there's a potential race condition if two users pull back the same object at the same time.not to view, but instead when they hit OK to invoke an action (the same action, or perhaps different, but at any rate on the same target object). Both of those users actions will pull back the object with the same version, but either one or the other will commit first, thereby bumping the version.

The race condition here is gonna be measured in milliseconds - it's the time between pulling an object back in order to interact with it, and then the transaction locking it out.

So, once the first user's transaction has completed, then the second user can interact with that object.

The concurrency check is to ensure that the object hasn't been modified since... and if it has, then to require the second unlucky user to start over.

This mechanism only protects the target object, but says nothing about the version of any other objects that might be involved in the transaction.