-
Notifications
You must be signed in to change notification settings - Fork 132
Add support for Optimistic Locking using @Version #93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please checkout how to format code and logs to keep the issue readable. Thank you. |
Potentially related to #87. |
Still, we need to sort out two things: The one is a bug that happens when you add |
This relates to https://jira.spring.io/browse/DATAJDBC-219 There is even someone working on it already spring-projects/spring-data-relational#124 |
https://github.com/spring-projects/spring-data-jdbc supports optimistic locking since version 2. Is there any information when optimistic locking will also be available for spring data r2dbc? |
Same problem, but looks like a different exception, looking forward to this being added |
Formatting. Added issue to test comments. Removed the test for presence of the id in case of a potential optimistic locking exception. A deleted row is also a case of a concurrent modification and therefore should trigger the OptimisticLockingException. Original pull request: #314.
Done. |
I have an entity bellow:
And controller like this:
When I save a Role without @Version everything is fine
But when I add @Version, it throws exception like this:
Source code demo:
https://github.com/roboticscm/r2dbc-reactive-redis.git
The text was updated successfully, but these errors were encountered: