Hey,
For the past five years, I've been using Django to manage a database of
online applications. I absolutely love it! Makes my job so much easier.
In general, any problems I run into, there's usually an easy workaround.
But I wonder if that's even feasible in this case. Anyway, here's the
pr
Thanks. #11652 is a good description of the same problem in the context of
the "change" page. I think that, in practice, it is more of a problem with
a list_editable, since you're updating many records at once. This makes a
"collision" with some other part of the system more likely.
I think the
I could see this feature being helpful. (Submitting the original data and
comparing it to be sure we don't silently have a merge conflict).
On Wed, Mar 16, 2016 at 11:14 PM, John C wrote:
> Thanks. #11652 is a good description of the same problem in the context of
> the "change" page. I think th
I know this particular case has been discussed before. Here are two related
tickets (I think there's a better canonical ticket but I can't find it just
now): https://code.djangoproject.com/ticket/11652
and https://code.djangoproject.com/ticket/16549
I haven't done the required reading recently,
