Hi, Those interested in this feature may find django-transaction-hooks [1] useful. It is my attempt to implement the commonly-useful case (run some code after the current transaction successfully commits, providing the code wasn't registered during a savepoint which was later rolled back.) I think the API provided by django-transaction-hooks is actually better for that use case than transaction signals are, since it does the work of handling some situations correctly (savepoints, closed connections), which in the case of signals are left up to the signal receiver to handle (or more likely, not bother to handle.)
Testing and feedback welcome. If this becomes widely used and seems to fill a need, I think there is a chance it could become part of Django core. (See #21803.) Carl [1] https://github.com/carljm/django-transaction-hooks -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/200b56e4-6577-451f-889d-d50678e77496%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
