#26043: Missing Middlewares for Changing Transaction Parameters
-------------------------------+--------------------------------------
Reporter: srkunze | Owner: nobody
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by charettes):
* status: new => closed
* resolution: => invalid
Comment:
Hi srkunze, [https://docs.djangoproject.com/en/1.9/internals/deprecation
/#deprecation-removed-in-1-8 TransactionMiddleware] has been deprecated
[https://docs.djangoproject.com/en/1.9/releases/1.6/#transaction-
management-apis since Django 1.6] in favor of the
[https://docs.djangoproject.com/en/1.9/topics/db/transactions/#tying-
transactions-to-http-requests ATOMIC_REQUESTS] settings which should do
exactly what you are expecting.
Please reopen if adding `ATOMIC_REQUESTS: True` to your `DATABASES`
setting aliases doesn't work for your.
--
Ticket URL: <https://code.djangoproject.com/ticket/26043#comment:2>
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.20dbb3319c87a1313eadb7bfe6a002ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
