| 76 | | ensure that Django has permission to create tables in the database |
|---|
| 77 | | you're using; if you plan to manually create the tables, you can |
|---|
| 78 | | simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and ``DELETE`` |
|---|
| 79 | | permissions. Django does not issue ``ALTER TABLE`` statements, and so |
|---|
| 80 | | will not require permission to do so. If you will be using Django's |
|---|
| 81 | | `testing framework`_ with data fixtures, Django will need permission |
|---|
| 82 | | to create a temporary test database. |
|---|
| | 76 | ensure that Django has permission to create and alter tables in the |
|---|
| | 77 | database you're using; if you plan to manually create the tables, you |
|---|
| | 78 | can simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and |
|---|
| | 79 | ``DELETE`` permissions. On some databases, Django will need to have |
|---|
| | 80 | ``ALTER TABLE`` privileges during ``syncdb`` (in order to create |
|---|
| | 81 | foreign key constraints properly on databases which do not allow them |
|---|
| | 82 | to be deferred), but will not issue ``ALTER TABLE`` statements on a |
|---|
| | 83 | table once ``syncdb`` has finished setting it up. |
|---|
| | 84 | |
|---|
| | 85 | If you will be using Django's `testing framework`_ with data fixtures, |
|---|
| | 86 | Django will need permission to create a temporary test database. |
|---|