#18392: Use utf8mb4 encoding with MySQL 5.5
-------------------------------------+-------------------------------------
Reporter: EmilStenstrom | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.4
(models, ORM) |
Severity: Normal | Resolution:
Keywords: utf8mb4 mysql | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
In case it's not clear, here's the problematic scenario I see:
* Indexes are created with max index name length=191 and truncated
accordingly.
* Developer increases max index name length setting to 200 (no changes to
index names in the database).
* Now migrations can't operate on existing indexes because the 200
character index names it generates aren't what's in the database.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:29>
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/071.b1f460140947d0a03f7827a5ce5bfa38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
