From e19fc9f08ab06f75eade82a122e7a4d0300ff860 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 5 Mar 2016 08:39:56 -0500 Subject: [PATCH] Removed claim that you can use different database backends for Django's tests. Such as a setup isn't tested through continuous integration and therefore isn't likely to work reliably. --- docs/internals/contributing/writing-code/unit-tests.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 8ed21549395..fb6fae1f72e 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -64,11 +64,9 @@ two databases: * A ``default`` database. This database should use the backend that you want to use for primary testing. -* A database with the alias ``other``. The ``other`` database is used to - establish that queries can be directed to different databases. As a result, - this database can use any backend you want. It doesn't need to use the same - backend as the ``default`` database (although it can use the same backend if - you want to). It cannot be the same database as the ``default``. +* A database with the alias ``other``. The ``other`` database is used to test + that queries can be directed to different databases. This database should use + the same backend as the ``default``, and it must have a different name. If you're using a backend that isn't SQLite, you will need to provide other details for each database: