+0 to extending the length, but the 255-character maximum in MySQL shouldn't be a concern since MySQL 5.0.3 (IIRC). I'm all for the ease of a length increase to the concern raised in the original post. While it would be nice to do more in the long term, that's a bigger discussion, as Aymeric points out.
I think it is also worth noting that creating a one-to-one UserProfile model or AbstractUser is significantly less intimidating to a newcomer and easier to change down the road than attempting an AbstractBaseUser implementation. Would it also be worth increasing the length of the `username` field to make email as username implementations easier, while we're on the topic? While Florian bring up some good points as well, there are years and years of legacy examples on the subject out there (Stack Overflow, for one) beyond the documentation that might make the larger change more appropriate for 2.0. Warm regards, Tim A. On Saturday, July 30, 2016 at 9:25:35 AM UTC-4, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas wrote: > > So I'm suggesting a change from 30 to 255 characters on last_name field, > which is the maximum possible without breaking backwards compatibility. > Maybe on Django 3 we can propose a change to "Full name" field ? > >> >> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/369bd1d4-4b5f-4a24-bd4f-85f8792582ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
