#27286: Tests fails when using multi-db and some DB is read-only
-----------------------------------+--------------------------------------
Reporter: Jose M Herrero | Owner: felixxm
Type: Bug | Status: assigned
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution:
Keywords: multi-db dbrouter | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by felixxm):
New algorithm for mySQL that determines whether the database supports
transactions, instead of `CREATE TABLE...` test
[https://github.com/django/django/pull/7320 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27286#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.77e8c680bb81fe0e2ffd75fc48d791ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
