#20846: Increase contrib.auth's User.username length
------------------------------+--------------------------------------
Reporter: ivoras@… | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 1.5
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by ivoras@…):
> This *isn't* as simple as the change you suggest. If we applied the diff
you describe, every Django user on the planet would need to issue a
migration on their database, which is a *massive* backwards
incompatibility.
Surely now that Django has a kind of built-in migration facility something
can be done about it?
> You're also then into the territory where you are discussing whether 150
characters is enough for a username. Email addresses, for example, can be
up to 254 characters and still be RFC compliant.
Great, I'd happy with 254 characters limit, and it would be future proof
as well.
I hope you realize that this change will have to be done sooner or later,
so better do it sooner?
--
Ticket URL: <https://code.djangoproject.com/ticket/20846#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.f7515a0b584d593199fb771fa4150867%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
