Optimistic Locking
- Fabrizio Niedda
By default the lasted saved update wins. We only update values that are actually detected as changed on the client and write back only those changes to the server. However, in some instances two users might edit the same object at the same time. In those situations they might override each other changes.
To prevent that simple locking is available that will fail to update if the object has been changed. This behaviour is making any distinction on whether user A edited property C and user B property D - the update will fail regardless of the properties affected.
To use optimistic locking on a class simple add the following to your class builder:
Elements.Person = Builder.Add.Class(nameof(Elements.Person))
// SNIP
.OptimisticLocking();Under the hood this will add an additional property with the name “Version” that is incremented on each update. If the version does not match what is currently stored in the database the update will fail and the client is notified that he needs to reload the object and re-apply the changes again.
