From 57aa1fd351d73feee947837d5dce5cfcb07af48e Mon Sep 17 00:00:00 2001 From: James Bennett Date: Fri, 15 Aug 2008 12:12:29 +0000 Subject: [PATCH] Fixed #6765: Changed docs/model-apit.txt to better indicate what's expected of initial SQL files. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8373 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/model-api.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/model-api.txt b/docs/model-api.txt index 8b6384f641..a203aa38c8 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -2113,9 +2113,9 @@ in an app called ``myapp``, you could add arbitrary SQL to the file INSERT INTO myapp_person (first_name, last_name) VALUES ('John', 'Lennon'); INSERT INTO myapp_person (first_name, last_name) VALUES ('Paul', 'McCartney'); -Each SQL file, if given, is expected to contain valid SQL. The SQL files are -piped directly into the database after all of the models' table-creation -statements have been executed. +Each SQL file, if given, is expected to contain valid SQL statements +which will insert the desired data (e.g., properly-formatted +``INSERT`` statements separated by semicolons). The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and ``reset`` commands in ``manage.py``. Refer to the `manage.py documentation`_