On 11/13/07, Gary Wilson <[EMAIL PROTECTED]> wrote: > How about introducing pre_save and/or post_save methods. The signal firing > happens in pre_save and post_save. You can override whatever you want - > pre_save, save, or post_save depending on your needs. This would also allow > you to disable the firing of signals by overriding pre/post_save with a no-op.
We had that, once upon a time, and it was probably more complex than it needed to be. Plus, you'd probably need to have save() call pre_save() and post_save() in order to make sure they all get called, which gets back into the problem of what happens when you override save(). -- "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 -~----------~----~----~----~------~----~------~--~---
