#27272: Protected objects not deleted even if they would have been deleted via
cascade anyway
-------------------------------------+-------------------------------------
Reporter: Daniel Izquierdo | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* component: Uncategorized => Database layer (models, ORM)
* needs_better_patch: => 0
* type: Uncategorized => Bug
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not sure. In the case of a conflict between `CASCADE` and `PROTECT`,
what general rule would you use? I guess a patch would help evaluate the
idea. The relevant code is
[https://github.com/django/django/blob/master/django/db/models/deletion.py
django/db/models/deletion.py].
--
Ticket URL: <https://code.djangoproject.com/ticket/27272#comment:1>
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/067.e7a8d7041e4a359f8d8b09558b0febeb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
