#27620: Add a TransactionMiddleware
------------------------------+-------------------------------------
Reporter: Tim Graham | Owner: luojiebin
Type: New feature | Status: assigned
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+-------------------------------------
Comment (by luojiebin):
But why the previous TransactionMiddleware was deprecated? Only because
ATOMIC_REQUESTS can do the same thing as it? But it can not noly apply to
views, but also other middleware, which ATOMIC_REQUESTS can't do. So, does
the previous TransactionMiddleware cause any problem so that we have to
deprecate it? With the new-style middleware, we can handle the previous
problem, or we can add new feature to TransactionMiddlware with it?
to [comment:4 Florian Apolloner]:
> @luojiebin That is to be decided, the main issue here - as you noted -
is supporting
[https://docs.djangoproject.com/en/1.10/topics/db/transactions/#django.db.transaction.non_atomic_requests
non_atomic_requests]. Any ideas welcome :D
--
Ticket URL: <https://code.djangoproject.com/ticket/27620#comment:5>
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/067.eeb1accf51b31584827198a9803a6fbb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
