Ticket #1263: db-renaming-doc-changes.2.diff

File db-renaming-doc-changes.2.diff, 4.7 KB (added by Malcolm Tredinnick <malcolm@…>, 12 years ago)

New patch including one missed case.

  • docs/authentication.txt

     
    394394
    395395Three basic permissions -- add, create and delete -- are automatically created
    396396for each Django model that has ``admin`` set. Behind the scenes, these
    397 permissions are added to the ``auth_permissions`` database table when you run
     397permissions are added to the ``auth_permission`` database table when you run
    398398``django-admin.py install [app]``. You can view the exact SQL ``INSERT``
    399399statements by running ``django-admin.py sqlinitialdata [app]``.
    400400
  • docs/flatpages.txt

     
    3535============
    3636
    3737``django-admin.py install flatpages`` creates two tables in your database:
    38 ``django_flatpages`` and ``django_flatpages_sites``. ``django_flatpages`` is a
     38``django_flatpage`` and ``django_flatpage_sites``. ``django_flatpage`` is a
    3939simple lookup table that essentially maps a URL to a title and bunch of text
    40 content. ``django_flatpages_sites`` associates a flatpage with a site.
     40content. ``django_flatpage_sites`` associates a flatpage with a site.
    4141
    4242The ``FlatpageFallbackMiddleware`` does all of the work. Each time any Django
    4343application raises a 404 error, this middleware checks the flatpages database
  • docs/legacy_databases.txt

     
    6666This won't work if your database already contains tables that have any of the
    6767following names:
    6868
    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``
    8079
    8180If that's the case, try renaming one of your tables to resolve naming
    8281conflicts. Currently, there's no way of customizing the names of Django's
  • docs/model-api.txt

     
    733733
    734734        db_table = "pizza_orders"
    735735
    736     If this isn't given, Django will use ``app_label + '_' + module_name``.
     736    If this isn't given, Django will use ``app_label + '_' + model_class_name``.
    737737
    738738    If your database table name is an SQL reserved word, or contains characters
    739739    that aren't allowed in Python variable names -- notably, the hyphen --
  • docs/redirects.txt

     
    2121How it works
    2222============
    2323
    24 ``django-admin.py install redirects`` creates a ``django_redirects`` table in
     24``django-admin.py install redirects`` creates a ``django_redirect`` table in
    2525your database. This is a simple lookup table with ``site_id``, ``old_path`` and
    2626``new_path`` fields.
    2727
  • docs/sessions.txt

     
    239239    * The session dictionary should accept any pickleable Python object. See
    240240      `the pickle module`_ for more information.
    241241
    242     * Session data is stored in a database table named ``core_sessions`` .
     242    * Session data is stored in a database table named ``django_session`` .
    243243
    244244    * Django only sends a cookie if it needs to. If you don't set any session
    245245      data, it won't send a session cookie.
  • docs/settings.txt

     
    563563
    564564Default: Not defined
    565565
    566 The ID, as an integer, of the current site in the ``sites`` database. This is
    567 used so that application data can hook into specific site(s) and a single
    568 database can manage content for multiple sites.
     566The ID, as an integer, of the current site in the ``django_site`` database
     567table. This is used so that application data can hook into specific site(s)
     568and a single database can manage content for multiple sites.
    569569
    570570TEMPLATE_CONTEXT_PROCESSORS
    571571---------------------------
Back to Top