James Bennett wrote: > 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().
I would think most use cases for overriding save() involve doing something before or after the actual saving of the object. In other words, having a pre_save() and post_save() means that few people would need to override save() at all. Gary --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
