#16713: Fixture loading for tests ignore database specific names.
-----------------------------------+------------------------------------
Reporter: brent@… | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 1.3
Severity: Normal | Resolution: invalid
Keywords: fixtures, multidb | 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` will be removed in Django 3.1 (see
b61ea56789a5825bd2961a335cb82f65e09f1614). Despite the fact that behavior
described in this ticket is still valid when using
[https://docs.djangoproject.com/en/2.2/topics/testing/tools/#django.test.TestCase.databases
TestCase.databases] it is also documented in
[https://docs.djangoproject.com/en/2.2/topics/testing/tools/#django.test.TransactionTestCase.databases
TransactionTestCase.databases] and
[https://docs.djangoproject.com/en/2.2/topics/testing/tools/#django.test.TransactionTestCase.fixtures
TransactionTestCase.fixtures], e.g.:
By default, fixtures are only loaded into the default database. If you
are using multiple databases and set TransactionTestCase.databases,
fixtures will be loaded into **all specified databases**.
--
Ticket URL: <https://code.djangoproject.com/ticket/16713#comment:3>
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/082.9a2be771e2687d336f4c8e855efe7a97%40djangoproject.com.
