Indeed! Perhaps nobody thought anyone would ever override the delete() method...
I'm not sure why the strategy is to gather together all the related objects and then do the SQL rather than call the delete() method on each of them. Perhaps its more efficient. Perhaps it avoids possible loops where two objects refer to each other, or perhaps its all done in one transaction to keep the DB consistent. I can't see a simple way of doing what would seem to be the 'right thing'. What you really need is some sort of 'pre_delete' method. Oh dear, those things seem to have disappeared with the 'magic-removal' code... Probably worth filing this as a bug... If its not there already, I cant find it! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users -~----------~----~----~----~------~----~------~--~---
