Apologies if this has come up before, I didn't find anything related in the archives.
As Model.save() is called both for inserts and updates, it would sometimes be useful for pre_save listeners to know whether the instance exists or not. This information is sent with post_save but by then it may be too late (e.g. under some conditions you may want to prevent an insertion from happening). In the current save_base() implementation, pre_save is sent before the instance's existence is determined, so I'm not sure if postponing it would break existing code. If there is no backwards compatibility issue, I can open a ticket and send a patch for it. George -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
