#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 Claude Paroz):
I suggest to begin with a very minimal patch like
[https://github.com/django/django/pull/8853 this PR], which will at least
allow users to begin converting some database columns to `utf8mb4` through
custom migrations, and use these columns in their code (where indexing
doesn't come in their way).
Working on index issues can come later, and will be needed to run the
Django test suite with `utf8mb4`.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:41>
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.676ad6b7218a2ac48435d877082515ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
