test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #23314 -- Tempered recommendation of storing profile data on custom user. 

Thanks gavinwahl for the report.
This commit is contained in:
Tim Graham 2014-08-19 07:23:17 -04:00
parent c587bd5a94
commit 3569536491
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/auth/customizing.txt
View File

@ -453,6 +453,8 @@ different User model.
:setting:`AUTH_USER_MODEL` setting in code that is executed at import
time. ``get_user_model()`` only works once Django has imported all models.
.. _specifying-custom-user-model:
Specifying a custom User model
------------------------------
@ -706,10 +708,12 @@ Extending Django's default User
-------------------------------
If you're entirely happy with Django's :class:`~django.contrib.auth.models.User`
model and you just want to add some additional profile information, you can
model and you just want to add some additional profile information, you could
simply subclass ``django.contrib.auth.models.AbstractUser`` and add your
custom profile fields. This class provides the full implementation of the
default :class:`~django.contrib.auth.models.User` as an :ref:`abstract model
custom profile fields, although we'd recommend a separate model as described in
the "Model design considerations" note of :ref:`specifying-custom-user-model`.
``AbstractUser`` provides the full implementation of the default
:class:`~django.contrib.auth.models.User` as an :ref:`abstract model
<abstract-base-classes>`.
.. _custom-users-and-the-built-in-auth-forms: