Hello, > On 30 Jul 2016, at 10:52, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas > <raonyguimar...@gmail.com> 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.
I’m -1 on basing the decision of “how long a last name does Django allow by default” on an unrelated technical limit. We’re discussing how long a reasonable last name is, not how many bytes MySQL can fit in a varchar without incurring an extra byte of overhead for storing the string length. I have trouble believing that a significant number of people are used to typing 100+ characters when inputting their name into a website — let alone that a significant number of people have a last name that contains more than 100 characters and that isn’t a joke. How would it fit on a passport? I know that Brazilian last names are commonly in the 30-50 characters range. Going for 60 to have a bit of margin makes sense. If my estimate is too low, we could go even further. But 100 and above doesn’t make sense to me. If you want to allow 255 characters in last names, in my opinion, you’re in the territory of custom user models. > Maybe on Django 3 we can propose a change to "Full name" field ? There’s a misconception about “Django 3” here. Django will guarantee the same compatibility between the last 2.x version and 3.0 than between 2.(x-1) and 2.x. Apart from that, I think that the most reasonable path to a built-in User model not based on first and last name is to ship a new model next to the current one and suggest that developers point AUTH_USER_MODEL to that model — or, even better, that they inherit the abstract version of the new built-in model in their project and point AUTH_USER_MODEL to their copy, so that they can make changes later if needed. Best regards, -- Aymeric. -- 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/4E860166-BE82-48AF-BF63-4EECC10B03DA%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
