Fixture loading for tests ignore database specific names.

[brent@…]

This is either a doc clarification bug, or a real bug. But based on this from the documentation:

Database-specific fixtures
If you are in a multi-database setup, you may have fixture data that you want to load onto one database, but not onto another. In this situation, you can add database identifier into . If your DATABASES setting has a ‘master’ database defined, you can define the fixture mydata.master.json or mydata.master.json.gz. This fixture will only be loaded if you have specified that you want to load data onto the master database.

This does not working during testing though. If you do not set multi_db = True, the fixtures are loaded into 'default' only. If you do set multi_db = True, all fixtures are loaded into all databases. There is no way to load some data into one database and some other data into the second as the above paragraph states.

If this is *really* a bug and just not the expected behavior and/or someone wants the expected behavior to change I could submit a patch. But I don't want to fix something that may not be broken.

Attached is a test project that shows the behavior.

[brent@…]

Test Project that show Fixture loading problems

[Aymeric Augustin]

This test shows how this feature works: https://code.djangoproject.com/browser/django/trunk/tests/regressiontests/multiple_database/tests.py#L1621

With the following changes, your tests pass:

--- testapp/tests.py.orig	2011-08-28 12:11:44.000000000 +0200
+++ testapp/tests.py	2011-08-28 12:11:02.000000000 +0200
@@ -12,7 +12,7 @@
     """
     multi_db = True
 
-    fixtures = ['people.default.json']
+    fixtures = ['people']
 
     def test_fixtures_loaded_to_default(self):
         """
@@ -35,7 +35,7 @@
     This should load the one into default only.
     """
 
-    fixtures = ['people.default.json']
+    fixtures = ['people']
 
     def test_fixtures_loaded_to_default(self):
         """
@@ -61,7 +61,7 @@
     """
     multi_db = True
 
-    fixtures = ['people.default.json', 'morepeople.core.json']
+    fixtures = ['people', 'morepeople']
 
     def test_fixtures_loaded_to_default(self):
         """

I think it's a bug. The docs say it's possible to pass only the "base name" of the fixture and let Django figure out the rest (database, format, compression); they don't say it's mandatory.

[anonymous]

Any hope of seeing this bug fixed?

[Mariusz Felisiak]

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 ​TestCase.databases it is also documented in ​TransactionTestCase.databases and ​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.