#14051: Signals for transaction commit/rollback
-------------------------------------+-------------------------------------
Reporter: Ask Solem <ask@…> | Owner: nobody
Type: New feature | Status: reopened
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
+1 for this. It would be useful for any kind of after-the commit
processing that is too large to be done in-band but even more importantly
the 'post save' will become much less of a gotcha because with a 'post
commit' people will realize that 'post save' does not occur after a
finalized transaction. Just knowing that upfront would have saved me a lot
of time!
--
Ticket URL: <https://code.djangoproject.com/ticket/14051#comment:17>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
