Fixed #13158 -- Clarified that OneToOneField is a better option for User profile classes. Thanks to hvdklauw for the report and patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13197 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
95fea01041
commit
b82a5b9dd0
|
@ -486,12 +486,13 @@ If you'd like to store additional information related to your users, Django
|
||||||
provides a method to specify a site-specific related model -- termed a "user
|
provides a method to specify a site-specific related model -- termed a "user
|
||||||
profile" -- for this purpose.
|
profile" -- for this purpose.
|
||||||
|
|
||||||
To make use of this feature, define a model with fields for the additional
|
To make use of this feature, define a model with fields for the
|
||||||
information you'd like to store, or additional methods you'd like to have
|
additional information you'd like to store, or additional methods
|
||||||
available, and also add a :class:`~django.db.models.Field.ForeignKey` from your
|
you'd like to have available, and also add a
|
||||||
model to the :class:`~django.contrib.auth.models.User` model, specified with
|
:class:`~django.db.models.Field.OneToOneField` from your model to the
|
||||||
``unique=True`` to ensure only one instance of your model can be created for
|
:class:`~django.contrib.auth.models.User` model. This will ensure only
|
||||||
each :class:`~django.contrib.auth.models.User`.
|
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
|
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
|
the setting :setting:`AUTH_PROFILE_MODULE` with a string consisting of the
|
||||||
|
|
Loading…
Reference in New Issue