diff options
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/migrations.txt | 2 | ||||
| -rw-r--r-- | docs/topics/testing/tools.txt | 9 |
2 files changed, 0 insertions, 11 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt index e1d13457b7..9c56574857 100644 --- a/docs/topics/migrations.txt +++ b/docs/topics/migrations.txt @@ -140,9 +140,7 @@ database to make sure they work as expected:: Apply all migrations: books Synchronizing apps without migrations: Creating tables... - Installing custom SQL... Installing indexes... - Installed 0 object(s) from 0 fixture(s) Running migrations: Applying books.0003_auto... OK diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 1f794701be..3fabf63c44 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -984,15 +984,6 @@ The most straightforward way of creating a fixture is to use the already have some data in your database. See the :djadmin:`dumpdata documentation<dumpdata>` for more details. -.. admonition:: Initial SQL data and testing - - Django provides a second way to insert initial data into models -- - the :ref:`custom SQL hook <initial-sql>`. However, this technique - *cannot* be used to provide initial data for testing purposes. - Django's test framework flushes the contents of the test database - after each test; as a result, any data added using the custom SQL - hook will be lost. - Once you've created a fixture and placed it in a ``fixtures`` directory in one of your :setting:`INSTALLED_APPS`, you can use it in your unit tests by specifying a ``fixtures`` class attribute on your :class:`django.test.TestCase` |