#27286: Tests fails when using multi-db and some DB is read-only
-----------------------------------+--------------------------------------
Reporter: Jose M Herrero | Owner: nobody
Type: Bug | Status: new
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 Tim Graham):
Do you have any ideas about how we could detect whether or not the
database supports transactions besides the
[https://github.com/django/django/blob/f2ff1b2fabbe26d5e61d690c4c5a47f9582f9300/django/db/backends/base/features.py#L238-L250
current algorithm] that requires creating a table?
--
Ticket URL: <https://code.djangoproject.com/ticket/27286#comment:2>
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.822f7f99f55fccaf2b7258e92a47602d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
