#30541: Django MultiDB tests not loading fixtures as expected.
-----------------------------------+--------------------------------------
Reporter: Vackar Afzal | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: master
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
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
* version: 2.2 => master
* resolution: => invalid
Comment:
Thanks for the report, however it works as
[https://docs.djangoproject.com/en/2.2/topics/testing/tools/#fixture-
loading documented] IMO.
If you set `TransactionTestCase.databases`, fixtures will be loaded into
all specified databases in your case `__all__`. If you want to run tests
and load fixtures only to the `default` db you should set `databases =
{'other'}` or completely remove `databases` (see also
[https://docs.djangoproject.com/en/2.2/topics/testing/tools/#multi-
database-support multi-database-support]).
Closing per TicketClosingReasons/UseSupportChannels.
--
Ticket URL: <https://code.djangoproject.com/ticket/30541#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 [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/069.43ac6487eadac98d23153449371da97e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
