From 75df13278caaceedd444c43c970c7d000f19b855 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Mon, 22 May 2006 02:24:32 +0000 Subject: [PATCH] Fixed #981 -- Documented backend-specific SQL files git-svn-id: http://code.djangoproject.com/svn/django/trunk@2953 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/model-api.txt | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/model-api.txt b/docs/model-api.txt index 6c674cb1aa..6ceabf4e3d 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -1658,4 +1658,25 @@ 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 +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 +separate initial-data files for PostgreSQL and MySQL. For each app, Django +looks for a file called ``/sql/..sql``, where +```` is your app directory, ```` is the model's name in +lowercase and ```` is the value of ``DATABASE_ENGINE`` in your +settings file (e.g., ``postgresql``, ``mysql``). + +Backend-specific SQL data is executed before non-backend-specific SQL data. For +example, if your app contains the files ``sql/person.sql`` and +``sql/person.postgresql.sql`` and you're installing the app on PostgreSQL, +Django will execute the contents of ``sql/person.postgresql.sql`` first, then +``sql/person.sql``.