#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
-------------------------------------+-------------------------------------
Changes (by MarkusH):
* status: new => closed
* resolution: => invalid
Comment:
I digged into the issue. It occurs on Postgres when the app with the
custom user model does not have migrations due to the dependency of your
user model on `auth.Group`. In accordance with the documentation this is
an unsupported behavior:
Be aware, however, that unmigrated apps cannot depend on migrated
apps, by the very nature of not having migrations. This means that it is
not generally possible to have an unmigrated app have a `ForeignKey` or
`ManyToManyField` to a migrated app; some cases may work, but it will
eventually fail.
https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies
I thus close this ticket as expected behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/24524#comment:5>
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.8eb42bc491269e0a584c2c40e26fee39%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
