>
> A whole other issue is how to handle the deletion of already deleted
> objects.
>
I misspoke here. I meant how to handle the deletion of an object with an
outdated version number. Should it raise the same exception?
--
You received this message because you are subscribed to the Google Gro
uot;matched vs. updated" issue goes away because
a matched row is also always updated by the version field being
incremented. Which drawbacks and edge cases can you see in such an solution?
A whole other issue is how to handle the deletion of already deleted
objects.
Best,
Rune Kaagaard
@Daniele
I struggled a bit with how to display the error message, and your solution
makes perfect sense.
Best,
Rune Kaagaard
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe
cket/11313
- [3] https://code.djangoproject.com/ticket/15574
-
[4] http://edgeapi.rubyonrails.org/classes/ActiveRecord/Locking/Optimistic.html
-
[5] http://api.rubyonrails.org/classes/ActiveRecord/Locking/Pessimistic.html
- [6] https://github.com/saxix/django-concurrency
- [7] https://github.c
