Ticket #1263: db-renaming-doc-changes.2.diff
| File db-renaming-doc-changes.2.diff, 4.7 KB (added by , 19 years ago) |
|---|
-
docs/authentication.txt
394 394 395 395 Three basic permissions -- add, create and delete -- are automatically created 396 396 for each Django model that has ``admin`` set. Behind the scenes, these 397 permissions are added to the ``auth_permission s`` database table when you run397 permissions are added to the ``auth_permission`` database table when you run 398 398 ``django-admin.py install [app]``. You can view the exact SQL ``INSERT`` 399 399 statements by running ``django-admin.py sqlinitialdata [app]``. 400 400 -
docs/flatpages.txt
35 35 ============ 36 36 37 37 ``django-admin.py install flatpages`` creates two tables in your database: 38 ``django_flatpage s`` and ``django_flatpages_sites``. ``django_flatpages`` is a38 ``django_flatpage`` and ``django_flatpage_sites``. ``django_flatpage`` is a 39 39 simple lookup table that essentially maps a URL to a title and bunch of text 40 content. ``django_flatpage s_sites`` associates a flatpage with a site.40 content. ``django_flatpage_sites`` associates a flatpage with a site. 41 41 42 42 The ``FlatpageFallbackMiddleware`` does all of the work. Each time any Django 43 43 application raises a 404 error, this middleware checks the flatpages database -
docs/legacy_databases.txt
66 66 This won't work if your database already contains tables that have any of the 67 67 following names: 68 68 69 * ``sites`` 70 * ``packages`` 71 * ``content_types`` 72 * ``core_sessions`` 73 * ``auth_permissions`` 74 * ``auth_groups`` 75 * ``auth_users`` 76 * ``auth_messages`` 77 * ``auth_groups_permissions`` 78 * ``auth_users_groups`` 79 * ``auth_users_user_permissions`` 69 * ``django_site`` 70 * ``django_content_type`` 71 * ``django_sessions`` 72 * ``auth_permission`` 73 * ``auth_group`` 74 * ``auth_user`` 75 * ``auth_message`` 76 * ``auth_group_permissions`` 77 * ``auth_user_groups`` 78 * ``auth_user_user_permission`` 80 79 81 80 If that's the case, try renaming one of your tables to resolve naming 82 81 conflicts. Currently, there's no way of customizing the names of Django's -
docs/model-api.txt
733 733 734 734 db_table = "pizza_orders" 735 735 736 If this isn't given, Django will use ``app_label + '_' + mod ule_name``.736 If this isn't given, Django will use ``app_label + '_' + model_class_name``. 737 737 738 738 If your database table name is an SQL reserved word, or contains characters 739 739 that aren't allowed in Python variable names -- notably, the hyphen -- -
docs/redirects.txt
21 21 How it works 22 22 ============ 23 23 24 ``django-admin.py install redirects`` creates a ``django_redirect s`` table in24 ``django-admin.py install redirects`` creates a ``django_redirect`` table in 25 25 your database. This is a simple lookup table with ``site_id``, ``old_path`` and 26 26 ``new_path`` fields. 27 27 -
docs/sessions.txt
239 239 * The session dictionary should accept any pickleable Python object. See 240 240 `the pickle module`_ for more information. 241 241 242 * Session data is stored in a database table named `` core_sessions`` .242 * Session data is stored in a database table named ``django_session`` . 243 243 244 244 * Django only sends a cookie if it needs to. If you don't set any session 245 245 data, it won't send a session cookie. -
docs/settings.txt
563 563 564 564 Default: Not defined 565 565 566 The ID, as an integer, of the current site in the `` sites`` database. This is567 used so that application data can hook into specific site(s) and a single 568 database can manage content for multiple sites.566 The ID, as an integer, of the current site in the ``django_site`` database 567 table. This is used so that application data can hook into specific site(s) 568 and a single database can manage content for multiple sites. 569 569 570 570 TEMPLATE_CONTEXT_PROCESSORS 571 571 ---------------------------