#26737: models.EmailField(unique=True) in custom AbstractBaseUser throws
auth.E003
during makemigrations
--------------------------------------------+--------------------
Reporter: MasterKale | Owner: nobody
Type: Bug | Status: new
Component: Core (Management commands) | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------------+--------------------
I'm trying to implement a custom AbstractBaseUser to replace the default
User class. For the most part I'm following the implementation detailed
[https://docs.djangoproject.com/en/1.9/topics/auth/customizing/#specifying-a
-custom-user-model here], with some additional fields and nothing for
'''REQUIRED_FIELDS''':
{{{
class Account(AbstractBaseUser):
email = models.EmailField(unique=True, db_index=True)
# ...snip...
USERNAME_FIELD = 'email'
}}}
Unfortunately when I run '''manage.py makemigrations''' I see the
following error:
{{{
pbapi.Account: (auth.E003) 'Account.email' must be unique because it is
named as the 'USERNAME_FIELD'.
}}}
I can suppress this error with the following:
{{{
SILENCED_SYSTEM_CHECKS = ['auth.E003']
}}}
This allows makemigrations to proceed, but I get the following output for
the '''email''' field:
{{{
class Migration(migrations.Migration):
initial = True
dependencies = [
]
operations = [
migrations.CreateModel(
name='Account',
fields=[
# ...snip...
('email', models.EmailField(max_length=254)),
}}}
When I modify the above migration output by hand to include unique=True:
{{{
fields=[
# ...snip...
('email', models.EmailField(max_length=254, unique=True)),
}}}
The next time I run makemigrations Django creates a migration that removes
that constraint:
{{{
operations = [
migrations.AlterField(
model_name='account',
name='email',
field=models.EmailField(max_length=254),
),
]
}}}
I'm not really sure what the culprit is. I've used this exact custom class
before in earlier versions of Django without issue (the latest Django I
can remember trying this in was 1.8), but for some reason Django 1.9 hates
this class. Am I doing something wrong?
--
Ticket URL: <https://code.djangoproject.com/ticket/26737>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.7a7192d119c1d30917dc2637b1596932%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
