From 7e8cf74dc74539f40f4cea53c1e8bba82791fcb6 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 26 Dec 2014 13:56:08 -0500 Subject: Removed support for syncing apps without migrations per deprecation timeline. Kept support for creating models without migrations when running tests (especially for Django's test suite). --- docs/topics/testing/tools.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 3fabf63c44..9d3ae456fd 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -670,12 +670,12 @@ to test the effects of commit and rollback: .. warning:: - ``TestCase`` running on a database that does not support rollback (e.g. MySQL with the - MyISAM storage engine), and all instances of ``TransactionTestCase``, will - roll back at the end of the test by deleting all data from the test database - and reloading initial data for apps without migrations. + ``TestCase`` running on a database that does not support rollback (e.g. MySQL + with the MyISAM storage engine), and all instances of ``TransactionTestCase``, + will roll back at the end of the test by deleting all data from the test + database. - Apps with migrations :ref:`will not see their data reloaded `; + Apps :ref:`will not see their data reloaded `; if you need this functionality (for example, third-party apps should enable this) you can set ``serialized_rollback = True`` inside the ``TestCase`` body. -- cgit v1.3