Concurrency is an issue in database systems where two users update the same record in the database, one after the other. If both users are viewing the same record, and then make independent changes, how the application handles concurrency determines which user’s data is updated in the record. In some applications, the second user to update a record will overwrite the changes made by the first. In others, the application will warn the second user that the record they are viewing has just been updated. In still others, the second user’s view is automatically updated when the first user updates the record.
|
|
|
Implementing concurrency handling is typically very tedious and must be applied carefully to nearly every transaction in an application. Iron Speed Designer creates optimistic concurrency handling code for each of your transactions so users cannot unintentionally overwrite each other's changes. |
Implementing concurrency handling is typically very tedious and must be applied carefully to nearly every transaction in an application. There are two commonly used concurrency detection and handling mechanisms: optimistic concurrency control and pessimistic concurrency control. Iron Speed Designer implements the optimistic concurrency model.
For more detail, see:
What is Pessimistic Concurrency?
