Ticket #4692: 4692.diff
| File 4692.diff, 2.5 KB (added by , 17 years ago) |
|---|
-
docs/install.txt
67 67 68 68 * If you're using Oracle, you'll need cx_Oracle_, version 4.3.1 or higher. 69 69 70 If you plan to use Django's ``manage.py syncdb`` command to 71 automatically create database tables for your models, you'll need to 72 ensure that Django has permission to create tables in the database 73 you're using; if you plan to manually create the tables, you can 74 simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and ``DELETE`` 75 permissions. Django does not issue ``ALTER TABLE`` statements, and so 76 will not require permission to do so. If you will be using Django's 77 `testing framework`_ with data fixtures, Django will need permission 78 to create a temporary test database. 79 70 80 .. _PostgreSQL: http://www.postgresql.org/ 71 81 .. _MySQL: http://www.mysql.com/ 72 82 .. _Django's ticket system: http://code.djangoproject.com/report/1 … … 78 88 .. _MySQL backend: ../databases/ 79 89 .. _cx_Oracle: http://www.python.net/crew/atuining/cx_Oracle/ 80 90 .. _Oracle: http://www.oracle.com/ 91 .. _testing framework: ../testing/ 81 92 82 93 Remove any old versions of Django 83 94 ================================= -
docs/testing.txt
137 137 that portions of it look like an interactive Python session, and execute those 138 138 lines while checking that the results match. 139 139 140 In the case of model tests, note that the test runner takes care of creating 141 its own test database. That is, any test that accesses a database -- by 142 creating and saving model instances, for example -- will not affect your 143 production database. Each doctest begins with a "blank slate" -- a fresh 144 database containing an empty table for each model. (See the section on 145 fixtures, below, for more on this.) 140 In the case of model tests, note that the test runner takes care of 141 creating its own test database. That is, any test that accesses a 142 database -- by creating and saving model instances, for example -- 143 will not affect your production database. Each doctest begins with a 144 "blank slate" -- a fresh database containing an empty table for each 145 model. (See the section on fixtures, below, for more on this.) Note 146 that to use this feature, the database user Django is connecting as 147 must have ``CREATE DATABASE`` rights. 146 148 147 149 For more details about how doctest works, see the `standard library 148 150 documentation for doctest`_