#21169: Deletion in custom reverse managers
-------------------------------------+-------------------------------------
Reporter: sebastian | Owner: loic84
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by loic84):
I've reworked M2M `RelatedManager.clear()` to account for the default
filtering through a subquery.
https://github.com/django/django/pull/1685
As previously noted, GFK and FK `RelatedManager.clear()` weren't affected
by the issue.
Also as discussed on IRC, `remove()` seems less critical since you specify
the objects manually, so we might get away with a warning in the docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/21169#comment:6>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.adaff3b80a2f372c29f78a2c5e9117e4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
