#27274: KeyError when using RenameModel in migrations that refer to an unmanaged
model in another app.
-------------------------------+--------------------------------------
Reporter: Dennis Ahrens | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | 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 Tim Graham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think the problem is mixing apps with and without migrations. You should
have migrations for `legacy`, even if the models aren't managed. After I
added and applied migrations for `legacy` (with Django 1.9.x), I had no
trouble running migrations on 1.10.
--
Ticket URL: <https://code.djangoproject.com/ticket/27274#comment:1>
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.adee28c2903708c0030ec3dd158176a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
