#21308: DatabaseError running tests with MySQL & utf8mb4 charset
-------------------------------------+-------------------------------------
Reporter: Greg Barker | Owner: nobody
<fletch@…> | Status: new
Type: Bug | Version: 1.5
Component: contrib.auth | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ramiro):
From http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html
''' Tip
To save space with UTF-8, use VARCHAR instead of CHAR. Otherwise, MySQL
must reserve three (or four) bytes for each character in a CHAR CHARACTER
SET utf8 (or utf8mb4) column because that is the maximum possible
length.'''
Django CharFields map to SQL CHAR. That would mean that the maximum
working max_length value in this particular case should be 191.
--
Ticket URL: <https://code.djangoproject.com/ticket/21308#comment:3>
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/093.c1d9991b126af035349b06dd4b905107%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
