#21169: Deletion in custom reverse managers
-------------------------------------+-------------------------------------
Reporter: sebastian | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by sebastian):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
In my patch proposal patch `r17204-custom-reverse-managers.diff` in #3871,
I considered the problem and then took the easy way out by simply
disallowing the `remove()` and `clear()` methods on custom reverse
managers. Obviously, this solution is far from perfect.
--
Ticket URL: <https://code.djangoproject.com/ticket/21169#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 [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.6985cee014984540061baf09a8a92f14%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
