#19822: USERNAME_FIELD should be validated as unique=True
--------------------------------------+------------------------------------
     Reporter:  russellm              |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  closed
    Component:  contrib.auth          |                  Version:  1.5-rc-1
     Severity:  Release blocker       |               Resolution:  fixed
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by cjerdonek):

 I also think this enforcement should be kept optional.  I created issue
 #21735 for this.  There I describe a second use case, in addition to the
 one by the anonymous poster above.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19822#comment:7>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.202a35ed28025ddc25fc8bcbcddbd0c7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to