#31335: Renaming a ForeignKey included in an index, and removing
UniqueConstraint,
Index with ForeignKey fails on MySQL.
-------------------------------------+-------------------------------------
Reporter: Stephen Finucane | Owner: Sergey
| Fursov
Type: Bug | Status: closed
Component: Migrations | Version: 3.0
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b731e8841558ee4caaba766c83f34ea9c7004f8b" b731e88]:
{{{
#!CommitTicketReference repository=""
revision="b731e8841558ee4caaba766c83f34ea9c7004f8b"
Fixed #31335 -- Fixed removing composed composed Meta constraints/indexes
on foreign keys on MySQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31335#comment:22>
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/0107018336313bbb-beb077e4-1715-450c-ae42-d9151cb81bc2-000000%40eu-central-1.amazonses.com.