#22689: inlines with sliced and ordered querysets save incorrectly when
underlying
data has changed since page load
-------------------------------+--------------------------------------
Reporter: cspinelive | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.7
Severity: Normal | Resolution:
Keywords: admin inline | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Ernest0x):
* status: closed => new
* version: 1.7-beta-2 => 1.7
* resolution: duplicate =>
Comment:
Replying to [comment:1 timo]:
> I think it's a probably a duplicate of #15574.
Why do you think this is a duplicate of #15574?
I am experiencing exactly the same behavior as the OP reports with 1.7.4
(inlines with slicing on the formset's queryset). In addition, in my case,
although the admin logs say that the objects were changed, in fact, they
were (re-)added as new (same values, different ids)! It seems that
something really bad is happening...
--
Ticket URL: <https://code.djangoproject.com/ticket/22689#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.d88c28195f35df28cb44caa8033a11f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
