django - specify database for TestCase fixtures

Question

I have two databases that my site uses and I have an app that uses both of them. I need to write a TestCase that loads fixtures for both databases. I use a DB router, which works fine in production, but in the testing framework, Django insists on using the 'default' database for all fixtures, even for models that specify the other database. How do I tell Django to run a fixture against another database?

My TestCase is defined list:

class VerifierTestCase(TestCase):
    fixtures = ['zipcodes_test.json', 'all_states.json', 'wtf.json']
    multi_db = True

Has anybody found an answer for this? Cannot get fixtures to not all load into 'default' — zenWeasel
– zenWeasel, Commented Jul 14, 2011 at 18:56

Jeffrey Bauer · Accepted Answer · 2011-11-30 20:15:59Z

5

There is actually a bug in Django that causes it to ignore the name-based db-specific pointers if you specify the entire fixture name.

so if you do fixtures = ["mydata.default.yaml", "mydata.myotherdatabase.yaml"]

It will load both fixtures into the default database.

But if you do fixtures = ['mydata']

It will load correctly. This is also true for dbengine specific filenames (e.g. mydata.default.postgresql.sql) as well.

edited Nov 30, 2011 at 20:15

Jeffrey Bauer

14.1k9 gold badges55 silver badges75 bronze badges

answered Nov 30, 2011 at 19:33

zenWeasel

1,8892 gold badges22 silver badges27 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

coredumperror Over a year ago

Unfortunately, this isn't true with Django 1.6. I get an error stating UserWarning: No fixture named 'migration_test_data' found when I try that.

ZZY Over a year ago

@CoreDumpError, I also got the warning, but, fixtures were loaded correctly. I think the warnings are kind of bug. I issued a ticket about it: code.djangoproject.com/ticket/24680#ticket

GDorn · Accepted Answer · 2011-07-21 20:09:11Z

2

Fixtures are targeted at specific databases by filename. This is true in TestCase instances as well, as they just call the loaddata command.

See https://docs.djangoproject.com/en/dev/ref/django-admin/#database-specific-fixtures

answered Jul 21, 2011 at 20:09

GDorn

8,8816 gold badges42 silver badges40 bronze badges

Comments

Kedar · Accepted Answer · 2022-10-28 08:54:33Z

0

If you have a multi-db setup with models exclusive to each database. You need to save a fixture file for each database (with the non-applicable database files being empty).

If your code defines fixtures = ["sample"] and you have two databases default and other.

You need two files: sample.default.json and sample.other.json. If sample contains only models from db default, sample.other.json will be an empty file ([]) and vice-versa.

Tried with Django 3.2

answered Oct 28, 2022 at 8:54

Kedar

1,70810 silver badges20 bronze badges

Collectives™ on Stack Overflow

django - specify database for TestCase fixtures

3 Answers 3

2 Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related