Hi all,
continuing my previous post, I've implemented most of the ideas mentioned in this thread
now, and would like, for completeness and future reference, add some related findings
and thoughts:
As mentioned in my previous post, reconstructing the formset's initial data (the
queryset) in t
Hi Tim,
Am 08.10.2015 um 21:03 schrieb Tim Graham:
I think the problem is also described in
https://code.djangoproject.com/ticket/15574.
Probably if we had a simple solution, that ticket wouldn't be open for 5 years.
:-)
:-)
Yes, having read all of it, I too think that #15574 describes the
Hi Daniel,
Am 08.10.2015 um 18:48 schrieb Daniel Roseman:
Can you explain further why you think the pk is not sufficient? Ordering by
name, or
adding and removing entities, does not change the pk of other entities; indeed
that's
the whole point of a pk. What exactly are you concerned about?
I think the problem is also described in
https://code.djangoproject.com/ticket/15574. Probably if we had a simple
solution, that ticket wouldn't be open for 5 years. :-)
On Thursday, October 8, 2015 at 12:48:34 PM UTC-4, Daniel Roseman wrote:
>
> Can you explain further why you think the pk is n
Can you explain further why you think the pk is not sufficient? Ordering by
name, or adding and removing entities, does not change the pk of other
entities; indeed that's the whole point of a pk. What exactly are you concerned
about?
--
DR.
--
You received this message because you are subscri
Dear Django fellows,
as far as I understand this, there seem to be two kinds of concurrency control:
- the one that occurs between request and save, as addressed by e.g. [1] and
[2],
- the one that occurs between GET request and POST request, especially with
formsets.
I'm currently trying
6 matches
Mail list logo
