#12339: ContentType update could cascade deletes to generic foreign keys, causing
data loss
-----------------------------------+--------------------------------------- -
          Reporter:  kcarnold      |         Owner:  nobody                      
            Status:  reopened      |     Milestone:                              
         Component:  Contrib apps  |       Version:  1.1                        
        Resolution:                |      Keywords:  contenttype, delete, cascade
             Stage:  Unreviewed    |     Has_patch:  0                          
        Needs_docs:  0             |   Needs_tests:  0                          
Needs_better_patch:  0             |  
-----------------------------------+--------------------------------------- -
Comment (by kcarnold):

 Pick your patch.

 The first one just removes the dangerous {{{delete}}}, always leaving
 stale content types alone.

 The second one keeps the {{{delete}}}, but guards it by a flag that
 defaults to False. It documents how to call the command with that flag
 being true. (It also incidentally enables {{{update_all_contenttypes}}} to
 pass along the new {{{db}}} parameter. I don't know if that's useful,
 though.) That documentation might arguably belong in the main docs, but I
 don't think it's worth integrating, given that it merely patches over the
 real problem (lack of migration support).

 I care that this bug is fixed, but I'm indifferent to which approach you
 prefer to take.

--
Ticket URL: <http://code.djangoproject.com/ticket/12339#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.