test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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
This commit is contained in:
James Bennett 2008-08-15 12:12:29 +00:00
parent 50b548d01b
commit 57aa1fd351
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/model-api.txt
View File

@ -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 ('John', 'Lennon');
INSERT INTO myapp_person (first_name, last_name) VALUES ('Paul', 'McCartney'); 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 Each SQL file, if given, is expected to contain valid SQL statements
piped directly into the database after all of the models' table-creation which will insert the desired data (e.g., properly-formatted
statements have been executed. ``INSERT`` statements separated by semicolons).
The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and
``reset`` commands in ``manage.py``. Refer to the `manage.py documentation`_ ``reset`` commands in ``manage.py``. Refer to the `manage.py documentation`_