Check out userena as well. But a custom authentication back-end was the approach I originally took. And to answer your question, yes -- your chances of finding people w/ email addresses longer than 75 chars are less than finding people w/ 30 chars -- but still a limitation none-the-less as there is no limitation on how long an email address can be.
On Wed, Oct 26, 2011 at 5:03 PM, Joakim Hove <[email protected]> wrote: > OK; > > thanks I was afraid it was not entirely straightforward. > > On Oct 26, 10:52 pm, Donald Stufft <[email protected]> wrote: > > This is a known limitation and it's something that people _want_ to get > fixed (but just merely increasing the length isn't helpful, because soon > someone comes along with the new length + 1 and the same problem occurs). > > Now - of course the problem can easily crop up again by just > increasing length; but if the username length and the email length at > least default to the same value (the email field has length 75) the > failure will at least be simultaneous - and the usage pattern I > describe will work until the 75 characters e-mail limit is reached. So > although by no means a full solution, increasing the username length > to 75 would in my opinion be a very simple fix with some benefit? > > Joakim > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
