#24524: Automatic migrations prevent creation of initial database table layout
-------------------------------------+-------------------------------------
Reporter: SimonSteinberger | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 1.8rc1
Severity: Normal | Resolution:
| worksforme
Keywords: migrations, fail, | Triage Stage:
collision | Unreviewed
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
Hi jbrendel,
From what I can see you have an application with no migrations
(`social_auth`) depending on an application with migrations (`accounts`)
which is not supported.
It looks like `social_auth` ships with migrations since at least `v0.2.0`,
which version are you using? Let's move this discussion to the #django IRC
channel instead, my nickname is `charettes`.
--
Ticket URL: <https://code.djangoproject.com/ticket/24524#comment:19>
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/074.f85bdc1b8cc52df7990d0754bf44bb65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
