test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #6927: Corrected documentation describing when and why the auth application creates default permissions 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@7388 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2008-03-30 13:35:12 +00:00
parent 502f0c18b0
commit 38d30e9691
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/authentication.txt
View File

@ -819,16 +819,17 @@ Django developers are currently discussing.
Default permissions
-------------------
Three basic permissions -- add, change and delete -- are automatically created
for each Django model that has a ``class Admin`` set. Behind the scenes, these
permissions are added to the ``auth_permission`` database table when you run
``manage.py syncdb``.
When ``django.contrib.auth`` is listed in your ``INSTALLED_APPS``
setting, it will ensure that three default permissions -- add, change
and delete -- are created for each Django model defined in one of your
installed applications.
Note that if your model doesn't have ``class Admin`` set when you run
``syncdb``, the permissions won't be created. If you initialize your database
and add ``class Admin`` to models after the fact, you'll need to run
``manage.py syncdb`` again. It will create any missing permissions for
all of your installed apps.
These permissions will be created when you run ``manage.py syncdb``;
the first time you run ``syncdb`` after adding ``django.contrib.auth``
to ``INSTALLED_APPS``, the default permissions will be created for all
previously-installed models, as well as for any new models being
installed at that time. Afterward, it will create default permissions
for new models each time you run ``manage.py syncdb``.
Custom permissions
------------------