#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 teeberg):
Replying to [comment:24 aigarius]:
> [...] have Django migration backend generate all the code for the
migration [...]
Even the utf8 to utf8mb4 migration, which would be the easiest in terms of
required changes, may cause data loss if you have indexes that are longer
than 191 characters and should thus probably be inspected and fixed up
individually and manually. For that reason, it seems impossible to me to
automate. That being said, clear migration instructions would probably be
helpful for many users.
Maybe this could be another backend-specific setting, similar to what was
implemented for integer types in 1506c71a95cd7f58fbc6363edf2ef742c58d2487?
Although, it only applying to index columns may make it way more painful
to implement.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:25>
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.4c12c064ac2004e776dd8838976306b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
