Replies: 3 comments 6 replies
-
|
Hey @eratio08, welcome!! I like the idea of constructing optimistic locking on top of |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Is there any progress? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Converted to issue #2897 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Motivation
Optimistic locking allows to handle competing/concurrent modifications of a row.
Proposed Solutions
Should generate the SQL statement
If effected row would be 0 the result be would be a
DbError::ConcurrentModificationA version column could be derived by
Additional Information
An advanced version could also allow Timestamps as data type for the opt-lock. The
opt_lockwould be updated vianow()/currentTimestampto avoid time shift issues of clients. Using a timestamp would allow to mergeopt_lockandmodified_at/updated_atcolumns into a single one.Beta Was this translation helpful? Give feedback.
All reactions