#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
Changes (by Tim Graham <timograham@…>):

 * status:  assigned => closed
 * resolution:   => fixed


 In [changeset:"82ce55dbbe2d96e8b5d1fcb4a1d52b73e08e7929" 82ce55d]:
 #!CommitTicketReference repository=""
 [1.10.x] Fixed #27558 -- Prevented redundant index on InnoDB ForeignKey.

 The MySQL backend overrides _field_should_be_indexed() so that it skips
 index creation for ForeignKeys when using InnoDB.

Ticket URL: <https://code.djangoproject.com/ticket/27558#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to