On Jun 16, 4:51 am, Jeremy Dunck wrote:
> On Tue, Jun 15, 2010 at 10:46 AM, George Sakkis
> wrote:
> > ...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 i
On Tue, Jun 15, 2010 at 10:46 AM, George Sakkis wrote:
> ...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
> tick
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 b
