diff options
| author | Tim Graham <timograham@gmail.com> | 2014-12-26 13:56:08 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-01-17 10:16:06 -0500 |
| commit | 4aa089a9a9504c4a833eee8161be013206da5d15 (patch) | |
| tree | ebc7e23d3805c57d9f6a4fc75767b5e5046617a4 /docs/topics/testing | |
| parent | a420f83e7d2e446ca01ef7c13d30c2ef3e975e5c (diff) | |
Removed support for custom SQL per deprecation timeline.
Diffstat (limited to 'docs/topics/testing')
| -rw-r--r-- | docs/topics/testing/tools.txt | 9 |
1 files changed, 0 insertions, 9 deletions
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` |
