#21961: Add support for database-level cascading options
-------------------------------------+-------------------------------------
Reporter: Christophe Pettus | Owner: Nick
| Stefan
Type: New feature | Status: assigned
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 IvanAnishchuk):
Just an idea, having two kwargs (on_delete/on_delete_db) is not entirely
different from having one kwarg and two sets of constants
(SET_NULL/SET_NULL_DB) -- we can always combine those constants like this:
on_delete=SET_NULL|SET_NULL_DB and have the described behavior without
adding a separate kwarg. Assuming it's appropriate in this case (although
it is the way Q objects are used, for example) and that having such
combinations is desirable at all (I could think of some cases but I'm not
sure I can remember any such in any of my recent projects).
--
Ticket URL: <https://code.djangoproject.com/ticket/21961#comment:20>
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.9bc2087f9f5b3d2816b6fb4d837e76c7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
