Fixed #15827 - Documented that OneToOneField in Profile should be named 'user'; thanks lawgon.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16155 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Timo Graham 2011-05-04 23:44:26 +00:00
parent 367e51e6a1
commit 127f1e4190
1 changed files with 2 additions and 2 deletions

View File

@ -467,8 +467,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`.