#22308: Transaction-related test failures on MySQL
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: aaugustin
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"83098dccdf3172302cde54e11c36050c1d83f996"]:
{{{
#!CommitTicketReference repository=""
revision="83098dccdf3172302cde54e11c36050c1d83f996"
[1.6.x] Fixed #23089 -- Fixed transaction handling in two management
commands.
Previously, when createcachetable and flush operated on non-default
databases, they weren't atomic.
Also avoided transactional DDL and transactional truncates on databases
that don't support them (refs #22308).
Backport of 753a22a635, 0757e0f30d, and 6877a9d415 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22308#comment:9>
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.4d1c0e87496967579acc0a216c014b53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
