#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) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: utf8mb4 mysql | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* stage: Design decision needed => Accepted
Comment:
This is just another case of MySQL being purposefully and irreversibly
brain-damaged. What it calls utf8 in actually a non-standard 3-bytes
encoding unrelated to utf8.
Django should give the option to use utf8mb4, and maybe recommend it in
the docs (if it works well; non-default features of MySQL rarely work
well).
The comments above suggest this isn't possible right now, although I'm
still confused as to the nature of the problem. Accepting on this basis.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:16>
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.
For more options, visit https://groups.google.com/groups/opt_out.
