Hi , I realize that django doesn't delete related objects when M2M field hasn't remaining relations. I don't see why django has this behaviour by default. I think it's a bit problematic because you can have 'orphan objects', and more over a change form for this object will raise a validation exception if you don't create a new relation.
Are anyone encouraged to explain a some good reason for this behavior? jeje What is the best way to avoid this? maybe overriding the save method but the down side of this is that admin delete confirmation page doesn't will be aware of this. Is there any other option? Thanks! -- Marc -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
