#26627: outermost atomic block executes on_commit callbacks registered in
another
outermost atomic block
-------------------------------------+-------------------------------------
Reporter: bartdag | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"a5c8072ab1e56da368a40f3e9c9a3b465f4ffbae" a5c8072a]:
{{{
#!CommitTicketReference repository=""
revision="a5c8072ab1e56da368a40f3e9c9a3b465f4ffbae"
Fixed #26627 -- Fixed on_commit callbacks execution order when callbacks
make transactions.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26627#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.a985aa9dbe338ed362a578ec6b4b6be6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
