On 7/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > It makes sense for anybody?, have anybody experimented something > similar?
This is actually what's supposed to happen; when you delete an object that's referred to by other objects, Djangos' behavior is to emulate the standard SQL 'ON DELETE CASCADE' and delete the referring objects. For some ideas that have been tossed around for changing this, see this thread on the developer list: http://groups.google.com/group/django-developers/browse_thread/thread/bae9fcc645c4b04c/c6ff82abf3570f4c And ticket #2288: http://code.djangoproject.com/ticket/2288 -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
