Ticket #3786: sqlinitialdata2.diff
| File sqlinitialdata2.diff, 2.2 kB (added by Ramiro Morales, 2 years ago) |
|---|
-
old-sqlinitialdata/docs/django-admin.txt
old new 332 332 333 333 Prints the CREATE TABLE and initial-data SQL statements for the given appnames. 334 334 335 Refer to the description of ``sql initialdata`` for an explanation of how to335 Refer to the description of ``sqlcustom`` for an explanation of how to 336 336 specify initial data. 337 337 338 338 sqlclear [appname appname ...] -
old-sqlinitialdata/docs/model-api.txt
old new 1915 1915 piped directly into the database after all of the models' table-creation 1916 1916 statements have been executed. 1917 1917 1918 The SQL files are read by the ``sql initialdata``, ``sqlreset``, ``sqlall`` and1918 The SQL files are read by the ``sqlcustom``, ``sqlreset``, ``sqlall`` and 1919 1919 ``reset`` commands in ``manage.py``. Refer to the `manage.py documentation`_ 1920 1920 for more information. 1921 1921 … … 1924 1924 time your custom data files are executed, all the database tables already will 1925 1925 have been created. 1926 1926 1927 .. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sql initialdata-appname-appname1927 .. _`manage.py documentation`: http://www.djangoproject.com/documentation/django_admin/#sqlcustom-appname-appname 1928 1928 1929 1929 Database-backend-specific SQL data 1930 1930 ---------------------------------- -
old-sqlinitialdata/docs/tutorial01.txt
old new 382 382 statements for this app. 383 383 384 384 * ``python manage.py sqlall polls`` -- A combination of all the SQL from 385 the 'sql', 'sql initialdata', and 'sqlindexes' commands.385 the 'sql', 'sqlcustom', and 'sqlindexes' commands. 386 386 387 387 Looking at the output of those commands can help you understand what's actually 388 388 happening under the hood.
