> Or is your main objection having to branch against the specific Simply put, there should be an *optional* way to ensure a model's *explicitly* defined delete behavior is honored without having to write hacks, signals, and/or patches of any kind (ie, make it DRY, and therefore less error-prone). This seems like common sense, so I really don't know how much more I can clarify the topic.
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
