#19707: TransactionMiddleware leaks transaction state
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.4
(models, ORM) | Resolution: fixed
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
More testing, and another option seems possible. Even if the connection
state cleaning doesn't succeed on the request that caused the error, it
will succeed in the next request that has a working connection available.
So, a request could still leak state to next request, but the next
successful request would then restore the connection to clear state (after
finish).
This seems good enough to me, what I hate is leaving the service in
permanent erroneous state, and that is avoided.
Still another option: how about doing the cleanup before request instead
after the request?
--
Ticket URL: <https://code.djangoproject.com/ticket/19707#comment:15>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
