#18556: .remove() on a reverse foreign key executes too many queries
-------------------------------------+-------------------------------------
Reporter: Alex | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.4
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* has_patch: 0 => 1
Comment:
+1 for this change. There are already situations where the signals
framework doesn't catch all changes. Using .update() in this situation
seems natural. On the other hand, I do not actually use signals...
If we wanted to keep signals for this, then we should have some sort of
pre/post update signal which one could use here. The signal would likely
have an argument of "objs" which would be lazily fetched from the DB - if
nobody access the objs then no extra work done.
The patch itself looks good to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/18556#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
