mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00
Code Issues 32 Releases Wiki Activity

Fixed #21755 -- Added ForeignKey support to REQUIRED_FIELDS.

Browse Source 
This allows specifying ForeignKeys in REQUIRED_FIELDS when using a
custom User model.

Thanks cjerdonek and bmispelon for suggestion and timgraham for review.
This commit is contained in:
Anubhav Joshi
2014-06-30 18:36:28 +05:30
committed by Tim Graham
parent 23d68c0f0d
commit 9bc2d766a0
6 changed files with 101 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -515,8 +515,7 @@ password resets. You must then provide some key implementation details:
will be prompted to supply a value for each of these fields. It must
include any field for which :attr:`~django.db.models.Field.blank` is
``False`` or undefined and may include additional fields you want
prompted for when a user is created interactively. However, it will not
work for :class:`~django.db.models.ForeignKey` fields.
prompted for when a user is created interactively.
``REQUIRED_FIELDS`` has no effect in other parts of Django, like
creating a user in the admin.
@@ -536,6 +535,15 @@ password resets. You must then provide some key implementation details:
``User`` model, but should *not* contain the ``USERNAME_FIELD`` or
``password`` as these fields will always be prompted for.
.. versionadded:: 1.8
:attr:`REQUIRED_FIELDS` now supports
:class:`~django.db.models.ForeignKey`\s. Since there is no way to pass
model instances during the :djadmin:`createsuperuser` prompt, expect the
user to enter the value of :attr:`~django.db.models.ForeignKey.to_field`
value (the :attr:`~django.db.models.Field.primary_key` by default) of an
existing instance.
.. attribute:: is_active
A boolean attribute that indicates whether the user is considered