#18392: Use utf8mb4 encoding with MySQL 5.5
-------------------------------------+-------------------------------------
Reporter: EmilStenstrom | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Accepted => Design decision needed
Comment:
I am marking this as design decision needed. This will need a good
solution which guarantees trouble-free upgrades for current users. While
it would be nice to have full UTF8 support with MySQL, I don't think it is
worth risking a breakage for existing users.
So, looking for good solutions here. Does MySQL infer the used character
set from some runtime variable (perhaps something set at CREATE DATABASE
time)? If so, we could just check the used charset for the db, and use
that for test database creation and index creation. If so, this would be a
simple solution to this problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/18392#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
