#21961: ForeignKey.on_delete supports database-level cascading options
-------------------------------------+-------------------------------------
Reporter: Xof | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Suor):
For me it actually ok that signals won't be called and some deletion
propagation could be broken. It's kind of `.raw()` and `.extra()` if you
mess with database you should handle all these things.
My use case is using a database with another non-django app. So I can't
rely on Djangos cascading.
--
Ticket URL: <https://code.djangoproject.com/ticket/21961#comment:7>
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/061.b97c3c718e55783a2210516f312c5818%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
