[1.5.X] Fixed #19279 - Clarified order of database setup and Django install.

Thanks colinnkeenan for the suggestion.

Backport of 72a6ac568d from master

1 files changed, 10 insertions, 8 deletions

diff --git a/docs/topics/install.txt b/docs/topics/install.txt
index b5573a8c4a..b71033f319 100644
--- a/docs/topics/install.txt
+++ b/docs/topics/install.txt
@@ -124,14 +124,16 @@ database bindings are installed.
 * If you're using an unofficial 3rd party backend, please consult the
   documentation provided for any additional requirements.
 
-If you plan to use Django's ``manage.py syncdb`` command to
-automatically create database tables for your models, you'll need to
-ensure that Django has permission to create and alter tables in the
-database you're using; if you plan to manually create the tables, you
-can simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and
-``DELETE`` permissions. On some databases, Django will need
-``ALTER TABLE`` privileges during ``syncdb`` but won't issue
-``ALTER TABLE`` statements on a table once ``syncdb`` has created it.
+If you plan to use Django's ``manage.py syncdb`` command to automatically
+create database tables for your models (after first installing Django and
+creating a project), you'll need to ensure that Django has permission to create
+and alter tables in the database you're using; if you plan to manually create
+the tables, you can simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and
+``DELETE`` permissions. On some databases, Django will need ``ALTER TABLE``
+privileges during ``syncdb`` but won't issue ``ALTER TABLE`` statements on a
+table once ``syncdb`` has created it. After creating a database user with these
+permissions, you'll specify the details in your project's settings file,
+see :setting:`DATABASES` for details.
 
 If you're using Django's :doc:`testing framework</topics/testing>` to test
 database queries, Django will need permission to create a test database.