#22970: Migration dependencies not correctly calculated
---------------------------------+----------------------------------------
Reporter: dekkers | Owner: andrewgodwin
Type: Bug | Status: new
Component: Migrations | Version: 1.7-rc-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Changes (by dekkers):
* status: closed => new
* resolution: fixed =>
Comment:
Your fix didn't work, when I ran migrate I got the following error:
{{{
KeyError: u"Dependency references nonexistent parent node (u'myapp1',
u'__last__')"
}}}
It looks like {{{__last__}}} isn't implemented, there isn't any other
mention of it in the source. I took a look at the code and fixed it in a
different way: get the name of the app's last migration from the graph and
use that. I did some quick tests and everything seems to work fine.
Pull request: https://github.com/django/django/pull/2917
--
Ticket URL: <https://code.djangoproject.com/ticket/22970#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 [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/065.341838018fd4bc7f082a41e33e07a3be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
