#21832: allow USERNAME_FIELD to be a ForeignKey
-------------------------------------+-------------------------------------
     Reporter:  cjerdonek            |                    Owner:
         Type:  New feature          |  anubhav9042
    Component:  contrib.auth         |                   Status:  closed
     Severity:  Normal               |                  Version:  master
     Keywords:                       |               Resolution:  fixed
  USERNAME_FIELD,ForeignKey,foreign  |             Triage Stage:  Accepted
  key,auth,username                  |      Needs documentation:  0
    Has patch:  1                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"75ff7b8fb8335e181ad05e1d4244b4295cc7a105"]:
 {{{
 #!CommitTicketReference repository=""
 revision="75ff7b8fb8335e181ad05e1d4244b4295cc7a105"
 Fixed #21832 -- Updated prompt, tests, and docs to show that
 USERNAME_FIELD supports FK after 9bc2d76.

 Also added get_input_data() hook in createsuperuser.

 Thanks Chris Jerdonek and Tim Graham for review.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21832#comment:17>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9e5d6678178f398231f3b681f4b5ce7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to