#25698: App without migrations depending on app with migrations fails on initial
migrate call (postgres)
----------------------------------+--------------------------------------
Reporter: lucasmoeskops | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: migrate postgres | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by charettes):
* status: new => closed
* resolution: => invalid
Comment:
This is
[https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies a
documented limitation].
> 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25698#comment:3>
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/071.1044242c5dcfe8175a1c781657a5e943%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
