#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: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by russellm):
* stage: Unreviewed => Accepted
* milestone: => 1.2
Comment:
I can't say I'm a fan of either current patch. Leaving content types
dangling like that doesn't strike me as a particularly friendly behavior,
especially given how easy it is to end up with stale content types during
initial development. I think a confirmation message is the way to go -
Yes, we need to be careful in the wording of the confirmation prompt, but
a broad "This is potentially destructive - If you're not sure, say 'NO'"
should be enough to prevent accidental damage.
So - I'd like see the contenttypes syncdb signal handler do the following:
* Gather a list of stale content types
* Print that list to the user
* Ask the user to confirm that the content types should be deleted
* on YES, delete the content types
* on NO, print a helpful message on how to manually purge.
--
Ticket URL: <http://code.djangoproject.com/ticket/12339#comment:8>
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.
