From 140e60e540a9508685d98a852b1fd44d83dd08c7 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Tue, 4 Dec 2007 06:07:44 +0000 Subject: [PATCH] Edited docs/install.txt changes from [6794] git-svn-id: http://code.djangoproject.com/svn/django/trunk@6877 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/install.txt | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/install.txt b/docs/install.txt index 7564f640bed..331a5ea8e36 100644 --- a/docs/install.txt +++ b/docs/install.txt @@ -76,14 +76,12 @@ 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 to have -``ALTER TABLE`` privileges during ``syncdb`` (in order to create -foreign key constraints properly on databases which do not allow them -to be deferred), but will not issue ``ALTER TABLE`` statements on a -table once ``syncdb`` has finished setting it up. +``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 will be using Django's `testing framework`_ with data fixtures, -Django will need permission to create a temporary test database. +If you're using Django's `testing framework`_ to test database queries, +Django will need permission to create a test database. .. _PostgreSQL: http://www.postgresql.org/ .. _MySQL: http://www.mysql.com/