diff options
| author | Collin Anderson <cmawebsite@gmail.com> | 2015-12-29 14:52:48 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-01-08 18:06:44 -0500 |
| commit | 780bddf75b93784470a2e352ed44ee35a751d667 (patch) | |
| tree | e492c7184f3743dc45194491ba52bcf833b3c4fd /docs/releases | |
| parent | ea7542891a4e3638a695c58bd6f00658b7c85985 (diff) | |
Fixed #20846 -- Decreased User.username max_length to 150 characters.
Diffstat (limited to 'docs/releases')
| -rw-r--r-- | docs/releases/1.10.txt | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/releases/1.10.txt b/docs/releases/1.10.txt index cf9b67d2d0..f3c7669d8a 100644 --- a/docs/releases/1.10.txt +++ b/docs/releases/1.10.txt @@ -354,13 +354,20 @@ to its proxied concrete class. This inconsistency was fixed by returning the full set of fields pointing to a concrete class or one of its proxies in both cases. -:attr:`AbstractUser.username <django.contrib.auth.models.User.username>` ``max_length`` increased to 254 +:attr:`AbstractUser.username <django.contrib.auth.models.User.username>` ``max_length`` increased to 150 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A migration for :attr:`django.contrib.auth.models.User.username` is included. If you have a custom user model inheriting from ``AbstractUser``, you'll need to generate and apply a database migration for your user model. +We considered an increase to 254 characters to more easily allow the use of +email addresses (which are limited to 254 characters) as usernames but rejected +it due to a MySQL limitation. When using the ``utf8mb4`` encoding (recommended +for proper Unicode support), MySQL can only create unique indexes with 191 +characters by default. Therefore, if you need a longer length, please use a +custom user model. + If you want to preserve the 30 character limit for usernames, use a custom form when creating a user or changing usernames:: |
