[1.3.X] Fixed #15827 - Documented that OneToOneField in Profile should be named 'user'; thanks lawgon.
Backport of r16155 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@16156 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
53354f80f6
commit
64e625b6a1
|
@ -476,8 +476,8 @@ 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.OneToOneField` from your model to the
|
||||
:class:`~django.contrib.auth.models.User` model. This will ensure only
|
||||
:class:`~django.db.models.Field.OneToOneField` named ``user`` 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`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue