#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 |
-------------------------------------+-------------------------------------
Comment (by donturner):
Replying to [comment:20 moggers87]:
> Replying to [comment:19 anonymous]:
> *snip*
> >
> > and {{{CREATE TABLE}}} or {{{ALTER TABLE}}} with the
{{{ROW_FORMAT=DYNAMIC}}} attribute.
> [[BR]]
> I'm not aware of any way to specify options like `ROW_FORMAT=DYNAMIC`
for create/alter statements in Django other than specifying `SET
ROW_FORMAT=DYNAMIC` with 'init_command' - but that adds overhead to each
connection (and feels a bit hacky imo)
Having run into the same issue my conclusion is that the only proper
solution is to switch to PostgreSQL. It would appear that MySQL has
extremely bad support for indexing on utf8mb4 fields.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:21>
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.694845d36998fec2aa65932ff58a91ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
