#26664: Support of model_object.delete(cascade=True)
-------------------------------------+-------------------------------------
Reporter: srkunze | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
This seems a bit dangerous to me. In particular, there's no way to control
how far or to which relations the deletions will cascade. I think it's
safer to explicitly handle the deletions in a use case like this. Of
course, you can also override the `Model.delete()` method to have whatever
behavior you like.
If you can find consensus on the DevelopersMailingList to add something
like this, I'll be happy to reopen the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/26664#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/065.6a2c1cf543129580a037fa1482aecfc5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
