#12339: ContentType update could cascade deletes to generic foreign keys,
causing
data loss
-----------------------------------+----------------------------------------
Reporter: kcarnold | Owner: nobody
Status: reopened | Milestone: 1.2
Component: Contrib apps | Version: 1.1
Resolution: | Keywords: contenttype, delete,
cascade
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by kcarnold):
* has_patch: 0 => 1
Comment:
I also prefer interactive; the attached patch is an (untested) shot.
It would be nice to only ask for confirmation if the {{{.delete}}} will
actually delete something. (Arguably it should ask for confirmation even
if it's just a permission entry, because you might forget to transfer
permissions to the new model. Agh, this really needs migration support to
do correctly!) I looked briefly at the delete confirmation code in admin,
but it looks too tightly woven into admin to use. Might make a feature
request for a more reusable "what else will this delete?" query, if there
isn't one already.
--
Ticket URL: <http://code.djangoproject.com/ticket/12339#comment:9>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
