mirror of
https://github.com/django/django.git
synced 2025-11-07 07:15:35 +00:00
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.
This commit is contained in:
committed by
Mariusz Felisiak
parent
af685b5f00
commit
3089018e95
@@ -248,7 +248,11 @@ Templates
|
||||
Tests
|
||||
~~~~~
|
||||
|
||||
* ...
|
||||
* The new ``serialized_aliases`` argument of
|
||||
:func:`django.test.utils.setup_databases` determines which
|
||||
:setting:`DATABASES` aliases test databases should have their state
|
||||
serialized to allow usage of the
|
||||
:ref:`serialized_rollback <test-case-serialized-rollback>` feature.
|
||||
|
||||
URLs
|
||||
~~~~
|
||||
@@ -313,7 +317,9 @@ Features deprecated in 4.0
|
||||
Miscellaneous
|
||||
-------------
|
||||
|
||||
* ...
|
||||
* ``SERIALIZE`` test 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.
|
||||
|
||||
Features removed in 4.0
|
||||
=======================
|
||||
|
||||
Reference in New Issue
Block a user