#12339: ContentType update could cascade deletes to generic foreign keys,
causing
data loss
-----------------------------------+----------------------------------------
Reporter: kcarnold | Owner: nobody
Status: closed | Milestone:
Component: Contrib apps | Version: 1.1
Resolution: duplicate | Keywords: contenttype, delete,
cascade
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Comment (by kcarnold):
I do very much appreciate that the management command does attempt to
clean up deleted content types, but until migrations are fully supported
there is no way for that command to know that deletion instead of renaming
occurred. So the current unconditional delete is already trying to support
schema migration. In contrast, someone who assumes that Django doesn't
support schema migration will assume that {{{syncdb}}} will only be
creating missing tables and otherwise won't touch anything, and will
certainly assume that it won't delete data. (I could see an argument that
the bug is in the docs, i.e., that a note should be added to the "Syncdb
will not alter existing tables" section.)
Until migrations are incorporated into base, the automatic content-type
deletion should require explicit confirmation. Then, if the confirmations
become annoying, making them automatic would be part of the migrations
effort
--
Ticket URL: <http://code.djangoproject.com/ticket/12339#comment:2>
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.
