From 2a0116266c4d81bd1cc4e3ea20efe9a7874f481b Mon Sep 17 00:00:00 2001 From: Mattia Cattarinussi Date: Fri, 29 Jun 2018 01:29:07 +0100 Subject: [PATCH] Refs #29513 -- Linked the testing docs from the multi-db topic guide. --- docs/topics/db/multi-db.txt | 5 +++++ docs/topics/testing/tools.txt | 2 ++ 2 files changed, 7 insertions(+) diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt index f857d29010..34320fb4d5 100644 --- a/docs/topics/db/multi-db.txt +++ b/docs/topics/db/multi-db.txt @@ -7,6 +7,11 @@ multiple databases. Most of the rest of Django's documentation assumes you are interacting with a single database. If you want to interact with multiple databases, you'll need to take some additional steps. +.. seealso:: + + See :ref:`testing-multi-db` for information about testing with multiple + databases. + Defining your databases ======================= diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 9591dac61c..8354771685 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -1108,6 +1108,8 @@ tests can't rely upon the fact that your views will be available at a particular URL. Decorate your test class or test method with ``@override_settings(ROOT_URLCONF=...)`` for URLconf configuration. +.. _testing-multi-db: + Multi-database support ----------------------