#33841: Django shouldn't fail (bulk-)update silently when QuerySet is already
evaluated / update documentation
-------------------------------------+-------------------------------------
Reporter: Shibel Karmi | Owner: nobody
Mansour |
Type: Uncategorized | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: update, bulk- | Triage Stage:
update, queryset | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => worksforme
Comment:
Thanks for the report, however it works for me. Maybe in
`initial_queryset` you filter out conditions that don't match any rows
after adding `MyOtherModel` instances, it's hard to tell. Please use one
of
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels] to debug your issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/33841#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070181f615ffb7-6666c234-3f8d-47b6-b3b3-299c27ee2b48-000000%40eu-central-1.amazonses.com.
