Author: russellm
Date: 2010-05-10 06:44:25 -0500 (Mon, 10 May 2010)
New Revision: 13200
Modified:
django/branches/releases/1.1.X/docs/topics/auth.txt
Log:
[1.1.X] Fixed #13158 -- Clarified that OneToOneField is a better option for
User profile classes. Thanks to hvdklauw for the report and patch.
Backport of r13197 from trunk.
Modified: django/branches/releases/1.1.X/docs/topics/auth.txt
===================================================================
--- django/branches/releases/1.1.X/docs/topics/auth.txt 2010-05-10 11:43:34 UTC
(rev 13199)
+++ django/branches/releases/1.1.X/docs/topics/auth.txt 2010-05-10 11:44:25 UTC
(rev 13200)
@@ -222,7 +222,7 @@
.. method:: models.User.has_perms(perm_list)
Returns ``True`` if the user has each of the specified permissions,
- where each perm is in the format
+ where each perm is in the format
``"<app label>.<permission codename>"``. If the user is inactive,
this method will always return ``False``.
@@ -264,7 +264,7 @@
.. method:: models.UserManager.create_user(username, email, password=None)
Creates, saves and returns a :class:`~django.contrib.auth.models.User`.
-
+
The :attr:`~django.contrib.auth.models.User.username` and
:attr:`~django.contrib.auth.models.User.password` are set as given. The
domain portion of :attr:`~django.contrib.auth.models.User.email` is
@@ -446,12 +446,13 @@
provides a method to specify a site-specific related model -- termed a "user
profile" -- for this purpose.
-To make use of this feature, define a model with fields for the additional
-information you'd like to store, or additional methods you'd like to have
-available, and also add a :class:`~django.db.models.Field.ForeignKey` from your
-model to the :class:`~django.contrib.auth.models.User` model, specified with
-``unique=True`` to ensure only one instance of your model can be created for
-each :class:`~django.contrib.auth.models.User`.
+To make use of this feature, define a model with fields for the
+additional information you'd like to store, or additional methods
+you'd like to have available, and also add a
+:class:`~django.db.models.Field.OneToOneField` from your model to the
+:class:`~django.contrib.auth.models.User` model. This will ensure only
+one instance of your model can be created for each
+:class:`~django.contrib.auth.models.User`.
To indicate that this model is the user profile model for a given site, fill in
the setting :setting:`AUTH_PROFILE_MODULE` with a string consisting of the
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
