Benjamin Slavin wrote: > On 5/30/07, Robert Coup <[EMAIL PROTECTED]> wrote: > >> So the post_create signal would be triggered *after* the transaction was >> committed? The patch in 2154 certainly doesn't handle that case. >> > > That's not what I was trying to communicate. It was mentioned that > you won't know if "the save is successful or not" if processing is > done in pre_save. > I agree that checking post_save/pre_save doesn't work too well around create. Do you think it's better to have a single post_create signal to go with post_save/pre_save or the two signals (save_update & save_insert) as per #2154? > If it's called as is done in the patch, the save has been successful > (assuming no future rollback), meaning that any problem wasn't with > persistence of the object. >
> Anyone needing to perform actions only after a successful commit is on > their own with the version of post_create being discussed. (I think > that's reasonable) > Fair enough :) Rob. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
