#21961: ForeignKey.on_delete supports database-level cascading options
-------------------------------------+-------------------------------------
Reporter: Xof | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version:
(models, ORM) | 1.7-alpha-1
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 shai):
1+2 => When using CASCADE_DB, signals will fire only on backends which do
not support the feature.
Similar issues, of course, for 1+3, 1+5.
I find this result quite disturbing.
Alternative: When using CASCADE_DB on a backend where the database cannot
implement it, Django tries to emulate it; this is ''not'' equivalent to
CASCADE.
--
Ticket URL: <https://code.djangoproject.com/ticket/21961#comment:5>
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.c2fc10ee76118a81161ddcb14c8caa14%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
