mirror of
https://github.com/django/django.git
synced 2024-12-01 15:42:04 +01:00
Fixed #5776: Added an explanation of when and why Django might need ALTER TABLE privileges to docs/install.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@6794 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
887c8ad565
commit
5f49d67427
@ -73,13 +73,17 @@ installed.
|
||||
|
||||
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 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. Django does not issue ``ALTER TABLE`` statements, and so
|
||||
will not require permission to do so. If you will be using Django's
|
||||
`testing framework`_ with data fixtures, Django will need permission
|
||||
to create a temporary test database.
|
||||
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.
|
||||
|
||||
If you will be using Django's `testing framework`_ with data fixtures,
|
||||
Django will need permission to create a temporary test database.
|
||||
|
||||
.. _PostgreSQL: http://www.postgresql.org/
|
||||
.. _MySQL: http://www.mysql.com/
|
||||
|
Loading…
Reference in New Issue
Block a user