Commits

Michael Manfre committed 2ae5e28

Documented backend specific `TEST_CREATE` setting

Comments (0)

Files changed (1)

docs/settings.txt

     will be able to see the plain-text password. Trusted connections are 
     recommended.
 
+.. setting:: TEST_CREATE
+
+TEST_CREATE
+~~~~~~~~~~~
+
+Default: ``True``
+
+This setting is specific to the `django-mssql` backend and controls whether or not
+the test database will be created and destroyed during the test creation. This is useful
+when integrating to a legacy database with a complex schema that is created by another
+application or cannot be easily created by Django's syncdb.
+
+
+.. code:: python
+
+    DATABASES = {
+        'default': {
+            'NAME': 'test_legacy_database',
+            'HOST': r'servername\ss2008',
+            'TEST_NAME': 'test_legacy_database',
+            'TEST_CREATE': False,
+        }
+    }
+
+.. note::
+
+    This is not intended to allow you to run tests against a QA, staging, or production database.
+
 .. setting:: OPTIONS
 
 OPTIONS
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.