The short answer is that Django doesn't provide any such protection
out of the box. There has been a little bit of discussion about this
feature (some of it over the last day or so), but a turnkey solution
is still a way off.
In the interim, you're might be able to hack together a solution using
a timestamp column on your model and a custom form field that renders
as a hidden field, and validates by comparing the existing instance
value with the value submitted in the form. However, you'll need to do
some experimentation here - I can't point you at any simple howto
documentation.
Yours,
Russ Magee %-)
> New Django user here with a question about the client side: Is there
> built-in support for dealing with concurrent edits? ...
>
Maybe you want the Django condition decorator, which lets you use HTTP
headers to send an ETag or Modified date and reject the updates if
they're not correct?
http://docs.djangoproject.com/en/dev/topics/conditional-view-processing/