#33903: Changing the related_name field causing pointless foreign key
re-creations
on MySQL migrations
-------------------------------------+-------------------------------------
Reporter: Thomas Aitken | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.2
Severity: Normal | Resolution: needsinfo
Keywords: migrations,foreign | Triage Stage:
key | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz):
* status: new => closed
* resolution: => needsinfo
Comment:
Django 2.2 is no longer supported. I didn't search the history, but have
the strong feeling that this is solved in recent Django versions. Do you
have the ability to test with more recent versions?
--
Ticket URL: <https://code.djangoproject.com/ticket/33903#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/010701827780155c-4bdef55f-a908-440b-853e-02e4ce4b2277-000000%40eu-central-1.amazonses.com.
