#24524: Automatic migrations prevent creation of initial database table layout
-------------------------------------+-------------------------------------
Reporter: SimonSteinberger | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8rc1
Severity: Release blocker | Resolution:
Keywords: migrations, fail, | Triage Stage:
collision | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by SimonSteinberger):
* status: closed => new
* resolution: invalid =>
Comment:
Well, I've digged into this myself now, and I must say: This is completely
nonsensical:
When using the AbstractUser class to create a custom user model *exactly
as outlined in Django's docs* at least the first "manage.py migrate" must
work and must create an empty database table layout. The sole purpose of
the AbstractUser class is to extend the basic user with more fields. But
as you describe it, the whole class is just useless and doomed to fail. By
teh way: Permissions and auth group tables are automatically created with
the AbstractUser model.
So, either I'm doing something plainly wrong here, or the docs are lacking
some critical information/solutions, or the whole construct doesn't male
sense as it is.
--
Ticket URL: <https://code.djangoproject.com/ticket/24524#comment:7>
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.7432a238b4e42d6fa874201d1dd76fe3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
