Ticket #5896: 5896.diff

docs/model-api.txt

@@ -2069 +2069 @@
 to populate default records, or create SQL functions, automatically.
 
 The hook is simple: Django just looks for a file called
-``<appname>/sql/<modelname>.sql``, where ``<appname>`` is your app directory and
+``<appname>/<modelname>.sql``, where ``<appname>`` is your app directory and
 ``<modelname>`` is the model's name in lowercase.
 
 In the ``Person`` example model at the top of this document, assuming it lives
 in an app called ``myapp``, you could add arbitrary SQL to the file
-``myapp/sql/person.sql``. Here's an example of what the file might contain::
+``myapp/person.sql``. Here's an example of what the file might contain::
 
     INSERT INTO myapp_person (first_name, last_name) VALUES ('John', 'Lennon');
     INSERT INTO myapp_person (first_name, last_name) VALUES ('Paul', 'McCartney');
@@ -2099 +2099 @@
 
 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 ``<appname>/sql/<modelname>.<backend>.sql``, where
+looks for a file called ``<appname>/<modelname>.<backend>.sql``, where
 ``<appname>`` is your app directory, ``<modelname>`` is the model's name in
 lowercase and ``<backend>`` 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``.
+Backend-specific SQL data is executed before non-backend-specific SQL data.
+For example, if your app contains the files ``person.sql`` and
+``person.postgresql.sql`` and you're installing the app on PostgreSQL, Django
+will execute the contents of ``person.postgresql.sql`` first, then
+``person.sql``.