#27901: Problem with Django models & MySQL & custom unicode classes
-------------------------------------+-------------------------------------
Reporter: Dominique Barton | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution:
Keywords: mysql, unicode, | Triage Stage:
error | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dominique Barton):
Additional info:
Switching from `mysql-python` to `mysqlcient` didn't help.
However, switching from python2 to python3 solves the issue.
This might be because in py3 everything is unicode by default (vs. byte
strings in py2) and the "default" type is unicode.
I'll try to migrate my project to py3 and the bug is gone. Unfortunately
it still exists with py2.
--
Ticket URL: <https://code.djangoproject.com/ticket/27901#comment:6>
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/068.76c5b68e6dfccdf770756826d3f3c627%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
