#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: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Unreviewed => Accepted
Comment:
Hmmh, lets just go for "forbid operations" approach. These methods can be
added back later on if we can fix them in clean way.
Actually, lets go for "no related manager methods" approach. You can also
do __set__ which could clear existing instances outside the manager's
viewable set, and .add() could add something that isn't viewable by the
manager.
--
Ticket URL: <https://code.djangoproject.com/ticket/21169#comment:4>
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/067.375d94803ad5ca0932030613d37f0ab3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
