#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 danros):

 I was just bitten by this!

 My situation involved moving some models from one app to another. I might
 have guessed that syncdb would have created a new contenttype for the
 models, but i didn't expect syncdb to cascade delete all affected items
 with a foreignkey referring the 'old' contenttype!

 IMO this should not be the default behaviour, or if it is, there should be
 *large* warnings about the possible loss of data.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/12339#comment:5>
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.


Reply via email to