#27835: Make TransactionTestCase raise an error if it accesses non-default
database
connection without multi_db=True
-----------------------------------+------------------------------------
Reporter: Tim Graham | Owner: nobody
Type: New feature | Status: closed
Component: Testing framework | Version: master
Severity: Normal | Resolution: invalid
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 felixxm):
* status: new => closed
* resolution: => invalid
Comment:
`multi_db` was removed in Django 3.1. Moreover `TransactionTestCase` with
a new `databases` attribute raises errors in such cases (see
8c775391b78b2a4a2b57c5e89ed4888f36aada4b).
--
Ticket URL: <https://code.djangoproject.com/ticket/27835#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.3f054ac3bff9fb27404f020fbe66d3ca%40djangoproject.com.
