#27859: Migration to create TextField with db_index=True crashes on MySQL
------------------------------------+------------------------------------
     Reporter:  Daniel Quinn        |                    Owner:  felixxm
         Type:  Bug                 |                   Status:  closed
    Component:  Migrations          |                  Version:  master
     Severity:  Normal              |               Resolution:  fixed
     Keywords:  mysql oracle index  |             Triage Stage:  Accepted
    Has patch:  1                   |      Needs documentation:  0
  Needs tests:  0                   |  Patch needs improvement:  0
Easy pickings:  0                   |                    UI/UX:  0
------------------------------------+------------------------------------
Changes (by GitHub <noreply@…>):

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


Comment:

 In [changeset:"538bf43458a147b7edeb7118c9f325c3f59ff6fb" 538bf434]:
 {{{
 #!CommitTicketReference repository=""
 revision="538bf43458a147b7edeb7118c9f325c3f59ff6fb"
 Fixed #27859 -- Ignored db_index for TextField/BinaryField on Oracle and
 MySQL.

 Thanks Zubair Alam for the initial patch and Tim Graham for the review.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/27859#comment:13>
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 
https://groups.google.com/d/msgid/django-updates/069.bfcf6b47809346db4c6ad1ade6b0386b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to