  order in which they're executed. The only thing you can assume is that, by the
  time your custom data files are executed, all the database tables already will
  have been created.
  
  .. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlinitialdata-appname-appname
  
  Database-backend-specific SQL data
  ----------------------------------
  
  There's also a hook for backend-specific SQL data. For example, you can have
 
</s> remove The SQL files are read by the ``sqlinitialdata``, ``sqlreset``, ``sqlall`` and
 </s> add The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and </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
.. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlcustom-appname-appname
  order in which they're executed. The only thing you can assume is that, by the
  time your custom data files are executed, all the database tables already will
  have been created.
  
.. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlcustom-appname-appname
  
  Database-backend-specific SQL data
  ----------------------------------
  
  There's also a hook for backend-specific SQL data. For example, you can have
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