1
0
mirror of https://github.com/django/django.git synced 2025-10-31 09:41:08 +00:00

[1.7.x] Doc edits for refs #22487.

Backport of c17cd151d8 from master
This commit is contained in:
Tim Graham
2014-06-09 12:09:16 -04:00
parent 0a515b02fc
commit 417da8a782
6 changed files with 21 additions and 13 deletions

View File

@@ -239,7 +239,7 @@ set ``atomic=False``.
.. warning::
RunPython does not magically alter the connection of the models for you;
``RunPython`` does not magically alter the connection of the models for you;
any model methods you call will go to the default database unless you
give them the current database alias (available from
``schema_editor.connection.alias``, where ``schema_editor`` is the second

View File

@@ -2121,17 +2121,19 @@ The name of the class to use for starting the test suite. See
TEST_NON_SERIALIZED_APPS
------------------------
.. versionadded:: 1.7
Default: ``[]``
In order to restore the database state between tests for TransactionTestCases
and database backends without transactions, Django will :ref:`serialize the
contents of all apps with migrations <test-case-serialized-rollback>` when it
starts the test run so it can then reload from that copy before tests that
need it.
In order to restore the database state between tests for
``TransactionTestCase``\s and database backends without transactions, Django
will :ref:`serialize the contents of all apps with migrations
<test-case-serialized-rollback>` when it starts the test run so it can then
reload from that copy before tests that need it.
This slows down the startup time of the test runner; if you have apps that
you know don't need this feature, you can add their full names in here (e.g.
``django.contrib.contenttypes``) to exclude them from this serialization
``'django.contrib.contenttypes'``) to exclude them from this serialization
process.
.. setting:: THOUSAND_SEPARATOR
@@ -3120,6 +3122,7 @@ Templates
Testing
-------
* Database: :setting:`TEST <DATABASE-TEST>`
* :setting:`TEST_NON_SERIALIZED_APPS`
* :setting:`TEST_RUNNER`
URLs