On Wed, 2010-08-18 at 17:16 +1000, Sam Lai wrote: > I was looking at this over the weekend as well; isn't a problem for me > but it seems that the post_save signal is triggered even when > commit=False. Therefore when the object is saved again with > commit=True, it is fired again. > > I didn't really investigate this so I could be wrong, but might be > something worth looking at.
well, in one model I am saving twice - so at least that is logical. But in the other, there is just one save - no commit=false. I read somewhere long time back that when a model is updated, django saves it twice. In which case it would be logical? > > On 18 August 2010 16:48, Kenneth Gonsalves <law...@au-kbc.org> wrote: > > hi, > > > > I am using a two post_save signal handlers for two different models. On > > certain conditions they have to send emails to me and others. At times > > one signal is generated, at other times two or even in one instance 4 > > signals were generated, which results in duplicate and triplicate > > emails. Has anyone faced this problem? > > -- > > regards > > Kenneth Gonsalves > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > > > > > -- regards Kenneth Gonsalves -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
