Code

Ticket #4692: 4692.diff

File 4692.diff, 2.5 KB (added by ubernostrum, 7 years ago)

Patch explaining necessary privileges

Line 
1Index: docs/install.txt
2===================================================================
3--- docs/install.txt    (revision 6248)
4+++ docs/install.txt    (working copy)
5@@ -67,6 +67,16 @@
6 
7 * If you're using Oracle, you'll need cx_Oracle_, version 4.3.1 or higher.
8 
9+If you plan to use Django's ``manage.py syncdb`` command to
10+automatically create database tables for your models, you'll need to
11+ensure that Django has permission to create tables in the database
12+you're using; if you plan to manually create the tables, you can
13+simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and ``DELETE``
14+permissions. Django does not issue ``ALTER TABLE`` statements, and so
15+will not require permission to do so. If you will be using Django's
16+`testing framework`_ with data fixtures, Django will need permission
17+to create a temporary test database.
18+
19 .. _PostgreSQL: http://www.postgresql.org/
20 .. _MySQL: http://www.mysql.com/
21 .. _Django's ticket system: http://code.djangoproject.com/report/1
22@@ -78,6 +88,7 @@
23 .. _MySQL backend: ../databases/
24 .. _cx_Oracle: http://www.python.net/crew/atuining/cx_Oracle/
25 .. _Oracle: http://www.oracle.com/
26+.. _testing framework: ../testing/
27 
28 Remove any old versions of Django
29 =================================
30Index: docs/testing.txt
31===================================================================
32--- docs/testing.txt    (revision 6248)
33+++ docs/testing.txt    (working copy)
34@@ -137,12 +137,14 @@
35 that portions of it look like an interactive Python session, and execute those
36 lines while checking that the results match.
37 
38-In the case of model tests, note that the test runner takes care of creating
39-its own test database. That is, any test that accesses a database -- by
40-creating and saving model instances, for example -- will not affect your
41-production database. Each doctest begins with a "blank slate" -- a fresh
42-database containing an empty table for each model. (See the section on
43-fixtures, below, for more on this.)
44+In the case of model tests, note that the test runner takes care of
45+creating its own test database. That is, any test that accesses a
46+database -- by creating and saving model instances, for example --
47+will not affect your production database. Each doctest begins with a
48+"blank slate" -- a fresh database containing an empty table for each
49+model. (See the section on fixtures, below, for more on this.) Note
50+that to use this feature, the database user Django is connecting as
51+must have ``CREATE DATABASE`` rights.
52 
53 For more details about how doctest works, see the `standard library
54 documentation for doctest`_