#32334: Backwards migration with RenameModel om MySQL failing with
content_type.name does not exist
-------------------------------------+-------------------------------------
Reporter: Gerben Morsink | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
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
-------------------------------------+-------------------------------------
Comment (by Gerben Morsink):
I found the actual error:
{{{ValueError: The field SomeOtherModel.new_model was declared with a lazy
reference to 'some_app.new_model', but app 'some_app' doesn't provide
model 'new_model'.}}}
I don't know why this actual error was hidden and the content_type.name
error was shown, but the cause was some manual editing on a migrations
file.
--
Ticket URL: <https://code.djangoproject.com/ticket/32334#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.842ff97541ab54b90b119a1ef1cb630b%40djangoproject.com.
