On Tue, 2007-11-13 at 22:58 -0600, Gary Wilson wrote: [...] > 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.
Your assessment of common use-cases is quite possibly correct, but it's already supported by the current code. Reintroducing pre_save and post_save doesn't remove the requirement that a developer can override save() -- now that the raw parameter exists -- so it's adding two extra methods that must always be called (or checked to see if they exist) without simplifying the root problem. Jeremy's still got a valid problem, though, but I'm not sure reintroducing pre_save() and post_save() is a necessary step yet. Hopefully there's something else we can do. Malcolm -- I've got a mind like a... a... what's that thing called? http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
