diff options
| author | Simon Charette <charette.s@gmail.com> | 2021-02-14 22:42:47 -0500 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-02-24 20:31:11 +0100 |
| commit | 3089018e951dcca568574c0e0ebf9d8aab112389 (patch) | |
| tree | 932c0c26621d115185561feded6987a57771a3ea /docs/ref | |
| parent | af685b5f00a2a38ec596ff905d5f70455185b6d7 (diff) | |
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.
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/settings.txt | 6 |
1 files changed, 6 insertions, 0 deletions
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 <test-case-serialized-rollback>`. +.. deprecated:: 4.0 + + This setting is deprecated as it can be inferred from the + :attr:`~django.test.TestCase.databases` with the + :ref:`serialized_rollback <test-case-serialized-rollback>` option enabled. + .. setting:: TEST_TEMPLATE ``TEMPLATE`` |