From 64e625b6a15da6848bda75941e2a5d8e781ac889 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Wed, 4 May 2011 23:44:54 +0000 Subject: [PATCH] [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 --- docs/topics/auth.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt index d1194345ff..d8e381b1a1 100644 --- a/docs/topics/auth.txt +++ b/docs/topics/auth.txt @@ -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`.