#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:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* type: Bug => Cleanup/optimization
* needs_tests: => 0
* needs_docs: => 0
Comment:
For Django's built in database backends, this issues seems to be limited
to MySQL as the other built in database backend set
`DatabaseFeatures.supports_transactions = True` and override the default
implementation which does
[https://github.com/django/django/blob/bd145e7209a0e628cced10384bd6f62d65c0f211/django/db/backends/base/features.py#L227-L239
the feature test] involving the temporary table indicated in the
traceback. Is it feasible to add a
`DatabaseFeatures.supports_transactions()` method for the MySQL backend
that detects transaction support by examining the storage engine?
--
Ticket URL: <https://code.djangoproject.com/ticket/26541#comment:1>
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.d2b03d56aa489a444f44cce6570855c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
