#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 akaariai):
I won't oppose an approach where checks framework will warn about
dangerous behavior.
For issue 1+2 mentioned by Shai in comment:5: we should disable signals
when cascading along CASCADE_DB converted to normal CASCADE due to not
having support for CASCADE by the backend.
--
Ticket URL: <https://code.djangoproject.com/ticket/21961#comment:8>
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.592c5b5902c73c2d88ba2eae74550fbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.