On 11/12/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > Perhaps Model.save(raw=False) should become Model.save(raw=False, > fire_signals=True), leaving it up to the overrider to decide the > policy?
Personally, I'm comfortable with documenting the fact that if Model.save() is never called, the pre_save and post_save signals will never fire (same is true of overridden __init__() and the post_init signal, and of overridden delete() and the pre_delete and post_delete signals). -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
