On Wed, Feb 15, 2012 at 10:37 PM, Donald Stufft <donald.stu...@gmail.com> wrote: > I know this has been discussed before, but I wanted to bring it up again in > light of the oncoming Djnago 1.4 beta. > > Can we increase the length of the username field in auth.User? > I think that a max_length of 75 (to match the default EmailField) would allow > developers > a lot more breathing room with regards to what they use as the value for > username.
75 isn't large enough these days for either email or username. We run a patched version of django for some time that has changed both these fields to 255 characters in order to accommodate the needs of our users. See RFC 3696. Schema migration concerns aside, it is a pity that Django continues to ship with a non conforming understanding of what an email may be. Personally, I believe this is a nonsense concern - if you state in the relnotes that a field has changed size, and that you must update your database schemas, **and people don't do it**, the only issue that can occur is that when a user attempts to use a longer email address or username the failure is an IntegrityError instead of a form error. Big whoop, should have read the relnotes. Each django "minor"* version release that I have updated through has included equally disruptive changes, I don't see why the prevarication over this one. I understand that the timing isn't great for this right now, but this is not an unknown or new problem. Another major release slips by without a fix for this. mañana, mañana… Cheers Tom * As in '1.1 -> 1.2', not as in 'insignificant version' -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
