#27274: KeyError when using RenameModel in migrations that refer to an unmanaged
model in another app.
-------------------------------+--------------------------------------
Reporter: Dennis Ahrens | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Normal | Resolution: invalid
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 Dennis Ahrens):
* status: new => closed
* resolution: => invalid
Comment:
Thank you for the reply. You are totally right - having migrations in the
legacy app solves the issue. It feels a little scary to have migrations
for a schema, where django should __not__ do anything with SQL, but on the
other hand it perfectly makes sense, that django needs information about
those migrations, if another app relies on this information within its
migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/27274#comment:2>
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.1786057b935254fb77c147830b76d7d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
