#34304: Adding and removing a conditional UniqueConstraint to ForeignKey
multiple
times crashes on MySQL
-------------------------------------+-------------------------------------
Reporter: Sage Abdullah | Owner: Sage
| Abdullah
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: GeyseR | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"5e0be0873ca6fe0c4ad7abe1398443bdf367d16e" 5e0be087]:
{{{
#!CommitTicketReference repository=""
revision="5e0be0873ca6fe0c4ad7abe1398443bdf367d16e"
[4.2.x] Fixed #34304 -- Made MySQL's SchemaEditor.remove_constraint()
don't create foreign key index when unique constraint is ignored.
Regression in b731e8841558ee4caaba766c83f34ea9c7004f8b.
Backport of 110b3b83567da22f19ec04210db134d0fe83d662 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34304#comment:6>
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/0107018607760e50-adfe76d1-ff43-4ba3-9d52-89126bf3c118-000000%40eu-central-1.amazonses.com.
