From dd839a2dfd6a30474a2b367a4b3ce70b26c3f318 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 11 Oct 2013 20:11:49 -0400 Subject: [PATCH] Fixed #15582 -- Documented how TransactionTestCase.multi_db affects fixtures. Thanks slinkp for the suggestion. --- docs/topics/testing/overview.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 420401cd4a..7735e2ab71 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -1229,6 +1229,10 @@ This flush/load procedure is repeated for each test in the test case, so you can be certain that the outcome of a test will not be affected by another test, or by the order of test execution. +By default, fixtures are only loaded into the ``default`` database. If you are +using multiple databases and set :attr:`multi_db=True +`, fixtures will be loaded into all databases. + URLconf configuration ~~~~~~~~~~~~~~~~~~~~~ @@ -1294,6 +1298,11 @@ For example:: This test case will flush *all* the test databases before running ``testIndexPageView``. +The ``multi_db`` flag also affects into which databases the +attr:`TransactionTestCase.fixtures` are loaded. By default (when +``multi_db=False``), fixtures are only loaded into the ``default`` database. +If ``multi_db=True``, fixtures are loaded into all databases. + .. _overriding-settings: Overriding settings