#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 Nick Stefan):
@Dylan
> or example, a very sensible scheme would be to have both
models.PROTECT_DB and models.CASCADE enabled
I do understand this desire. The existing foreign key constraints that get
added for models.CASCADE, only help you when you later go to edit a row
with one of those not valid foreign keys. It wont enforce / protect you
when models.CASCADE doesn't get all of the rows it should have. I hadn't
considered that there could be a desire for DB_DELETE that is completely
outside performance desires.
Is that a fair characterization?
--
Ticket URL: <https://code.djangoproject.com/ticket/21961#comment:19>
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.9663db902935fa46de8c08591390c8be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
