#27558: Setting db_index=False on existing ForeignKey causes constraint to be
recreated on MySQL
-------------------------------------+-------------------------------------
Reporter: Ed Morley | Owner: Ed Morley
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: db-indexes, mysql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"4086ff9ecbf4824cc5c0cc94e4c13ef474a22b9b" 4086ff9e]:
{{{
#!CommitTicketReference repository=""
revision="4086ff9ecbf4824cc5c0cc94e4c13ef474a22b9b"
[1.10.x] Refs #27558 -- Isolated indexes test on MySQL.
MySQL schema changes must be done in TransactionTestCase.
Backport of f94475e5262abe78d9771bc353f741b20cc3c725 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27558#comment:9>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.c18ea30f3be5e69ed5382a8e985b5b8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
