Concurrent update on record
Draft Disclaimer: Please note that this article is currently in draft form and may undergo revisions before final publication. The content, including information, opinions, and recommendations, is subject to change and may not represent the final version. We appreciate your understanding and patience as we work to refine and improve the quality of this article. Your feedback is valuable in shaping the final release.
Language Mismatch Disclaimer: Please be aware that the language of this article may not match the language settings of your browser or device.
Do you want to read articles in English instead ?
Concurrent update on record
- how the database handles it
- how your applications handles it
- how we can prevent data loss from that
A solution: full lock
- have a single point of edition
- lock at the application level whenever the edit page is opened
- pro: consistent
- cons: doesn't allow concurrency
- library: model lock package for library (TODO: insert link)
Better solution: partial lock
- have multiple point of edition (can be same page)
- example: user edit page segmented into the following sections
- info ie names and coordinates
- addresses
- notifications
- system preferences
- lock by section instead locking the whole app
- pro: consistent, allow concurrency as long as it is not on the same section
- makes sens to lock partially
By Babacar Cissé DIA
on