user 1 opens object1 admin page and make edits
user 2 opens object1 admin page and make edits
user 1 submits
user2 submits
Attached is PR to give an error when user2 saves, since he does not save
the recent version. I'm not sure if this protection should be protected in
options flag.
We'll be happy for comments.
--
Ticket URL: <https://code.djangoproject.com/ticket/32867>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: nobody => Eran Keydar
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/32867#comment:1>
* type: Uncategorized => New feature
* component: Uncategorized => contrib.admin
--
Ticket URL: <https://code.djangoproject.com/ticket/32867#comment:2>
Comment (by Eran Keydar):
This is the PR https://github.com/django/django/pull/14541
If if seems like good direction, I will add tests before merge (tested
manually so far).
The PR adds one DB access to the admin page, 2 tests chagend accordingly.
--
Ticket URL: <https://code.djangoproject.com/ticket/32867#comment:3>
Comment (by Alexandr Tatarinov):
IMHO this kind of functionality should be implemented as a 3rd party
library.
Also, I believe there are better ways to implement concurrency protection
(i.e. optimistic locking via some `version` field), which will also handle
other sources of editing, not just the admin.
--
Ticket URL: <https://code.djangoproject.com/ticket/32867#comment:4>
* status: assigned => closed
* resolution: => duplicate
Comment:
Duplicate of #11652.
--
Ticket URL: <https://code.djangoproject.com/ticket/32867#comment:5>