#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
-------------------------------------+-------------------------------------
Changes (by kezabelle):
* cc: django@… (added)
Comment:
By way of consensus: I agree that if possible, going forward, Django ought
to seek to use utf8mb4, because for better or worse, the world is becoming
more mobile oriented, and with it more emoji-laden; the non-mb4
charsets/collations choke on such things, which is just plain unfortunate.
If a suitable backwards-compatible, migration-friendly patch can't be
achieved, it should at least be mentioned in the docs somewhere, IMHO
(searching for `utf8mb4` or `emoji` currently yields no results, so I
assume there are none squirreled away). Whether that mention is a
recommendation or not is probably still unclear.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:35>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.e805b98bd5a7888c194fe1df0b9a161f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
