  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.
  
  The SQL files are read by the ``sqlinitialdata``, ``sqlreset``, ``sqlall`` and
  ``reset`` commands in ``manage.py``. Refer to the `manage.py documentation`_
  for more information.
  
  Note that if you have multiple SQL data files, there's no guarantee of the
  order in which they're executed. The only thing you can assume is that, by the
 
</s> remove       the 'sql', 'sqlinitialdata', and 'sqlindexes' commands.
 </s> add       the 'sql', 'sqlcustom', and 'sqlindexes' commands. </s> remove Refer to the description of ``sqlinitialdata`` for an explanation of how to
 </s> add Refer to the description of ``sqlcustom`` for an explanation of how to </s> remove .. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlinitialdata-appname-appname
 </s> add .. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlcustom-appname-appname
The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and
  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.
  
The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and
  ``reset`` commands in ``manage.py``. Refer to the `manage.py documentation`_
  for more information.
  
  Note that if you have multiple SQL data files, there's no guarantee of the
  order in which they're executed. The only thing you can assume is that, by the
keep keep keep keep replace keep keep keep keep keep
 Fixed #3786 -- Fixed sqlinitialdata references in some docs. Thanks, Ramiro Morales

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5004 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/model-api.txt