#26541: Add a DatabaseFeatures.supports_transactions() method for MySQL
-------------------------------------+-------------------------------------
Reporter: marcinn | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
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
-------------------------------------+-------------------------------------
Changes (by timgraham):
* stage: Unreviewed => Accepted
Comment:
I don't have much MySQL expertise so I'm afraid I can't advise much here
but I don't think Django needs to support the use case of per table
transaction handling. If someone has such a need, perhaps that could be
accomplished by routing to different database aliases.
As a workaround until a solution lands in Django, you could create your
own MySQL backend that sets `support_transaction` as you like. Unless a
discussion on the DevelopersMailingList reaches a different consensus, I
don't think adding something in `OPTIONS` makes sense given that this
doesn't seem to be much of an issue as far as tell. I haven't seen anyone
else hit this problem since the current technique was introduced in Django
1.1 (344f16e2205a4959ba65d975716a38db77d2061e).
--
Ticket URL: <https://code.djangoproject.com/ticket/26541#comment:3>
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.234b33a1664fd36bb72228f83e083a6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
