#24410: MySQL manually created indexes aren't recognized
----------------------------+--------------------------------------
Reporter: karolyi | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => duplicate
Comment:
It seems that the MySQL warning about the index name being too long is
tracked in #18392. Note that MySQL warnings are no longer promoted to
errors in DEBUG mode as of #23871 (in 1.8); however, you could work around
this on 1.7 by running your migrations with `DEBUG=False`. I think all the
issues presented in this ticket are duplicated of other tickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/24410#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
https://groups.google.com/d/msgid/django-updates/065.4955794f1ca5ff307f154b5c7ba6ac8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
