The past week , I did concurrency tests , automatically creating item names with concatenating strings , set bindings and some UI updating .
UI updates were setting auto-generated item names to read-only so user cannot edit textboxes , adding new textboxes with new property. Also, adding migration to the database with the latest updated property .
String concatenating (meaning linking a string in a chain or series) is to join different property of strings together , while implementing the logic in Wrappers to save different strings concatenated into database.
The concurrency problem I faced was when two users execute a transaction simultaneously . Ideally in this situation, the first user transaction will succeed and the second will fail .The common concurrency problems that potentially happen in DBMS transactions are usually :
- Temporary Update Problem
- Incorrect Summary Problem
- Lost Update Problem
- Unrepeatable Read Problem
- Phantom Read Problem
https://www.geeksforgeeks.org/concurrency-problems-in-dbms-transactions/
However , one way to fix a concurrency problem is when the second user fails transaction , is to reload its transaction entry . Then resave it by clicking the save button again .