#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 collinanderson):
For a first step, I propose a a setting in DATABASES OPTIONS that tells
Django the maximum index size to use when creating new indexes. I think it
should default to 191. That way Django won't ever reduce the size of
existing indexes, only new indexes.
If we have that settings, it's at least _possible_ to use utf8mb4. We
could then down the road have Django try to default to using utf8mb4
encoding for new databases/tables/columns.
(We need this for #20846.)
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:26>
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.3e96afb03d76af3560ed239342ce1ec5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
