From 3089018e951dcca568574c0e0ebf9d8aab112389 Mon Sep 17 00:00:00 2001 From: Simon Charette Date: Sun, 14 Feb 2021 22:42:47 -0500 Subject: Fixed #32446 -- Deprecated SERIALIZE test database setting. Whether or not the state of a test database should be serialized can be inferred from the set of databases allowed to be access from discovered TestCase/TransactionTestCase enabling the serialized_rollback feature which makes this setting unnecessary. This should make a significant test suite bootstraping time difference on large projects that didn't explicitly disable test database serialization. --- docs/ref/settings.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index 3f18af978d..18eb941ce8 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -821,6 +821,12 @@ the database state between tests if you don't have transactions). You can set this to ``False`` to speed up creation time if you don't have any test classes with :ref:`serialized_rollback=True `. +.. deprecated:: 4.0 + + This setting is deprecated as it can be inferred from the + :attr:`~django.test.TestCase.databases` with the + :ref:`serialized_rollback ` option enabled. + .. setting:: TEST_TEMPLATE ``TEMPLATE`` -- cgit v1.3