#24524: Automatic migrations prevent creation of initial database table layout
-------------------------------------+-------------------------------------
Reporter: SimonSteinberger | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8rc1
Severity: Release blocker | Resolution: invalid
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
-------------------------------------+-------------------------------------
Comment (by SimonSteinberger):
You're right - those are PostgreSQL driven app. Can you point me into the
right direction how to avoid this issue, when using a very simple
AbstractUser model without any additional fields?
I think that's a pretty normal use case. A solution should be pointed out
in the documentation. And despite I'm pretty experienced with Django in
general (and very happy with it), I can't see how to avoid this problem
...
--
Ticket URL: <https://code.djangoproject.com/ticket/24524#comment:6>
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.f64ada3531207c006ff1d1f60d26e870%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
