#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Adam Johnson (added)
* status: new => closed
* resolution: => invalid
Comment:
Thanks for the ticket, however Django 2.2 doesn't receive bugfixes
anymore. Also, Django doesn't use `ContentType.name` anymore, so this can
be an issue with some incompatible 3rd party package.
Closing per TicketClosingReasons/UseSupportChannels.
--
Ticket URL: <https://code.djangoproject.com/ticket/32334#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f3770607d422805f5aa6d57f384c7b1b%40djangoproject.com.
