#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:"dd2e4d7b5d6f24f33c2805b0bfb97a08e27b2125" dd2e4d7b]:
 #!CommitTicketReference repository=""
 Refs #27558 -- Added test for no index on InnoDB ForeignKey.

 The refactor in 3f76d1402dac9c2993d588f996dc1c331edbc9a7 fixed the
 of redundant indexes.

 Forwardport of 82ce55dbbe2d96e8b5d1fcb4a1d52b73e08e7929 from stable/1.10.x

Ticket URL: <https://code.djangoproject.com/ticket/27558#comment:7>
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