#8340: MySQL case sensitivity and utf8_bin / 2710
------------------------------------+---------------------------------------
Reporter: hrauch | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by hrauch):
I do understand your time-line arguments. But the problem with utf8_bin
seems to be more complicated:
When I changed most of our var chars field to utf8_bin on my developing
system (SuSE 11), everything works fine. But if I do the same with our
production server (Ubuntu 8.04), I'll sometimes get UnicodeDecodeErrors,
since some of the var char fields do return normal strings instead of
unicode strings. Both systems use the same django version; both systems
use the same database by dumping and restorung the database.
If I turn back theses fields from utf8_bin to ut8_unicode_ci, the
production system works well again.
Another problem: If I use utf8_bin for a field and use the query operator
__iexect, it does work correctly.
So I must say, that case sensitivity with mysql and utf8_bin doesn't work
well.
--
Ticket URL: <http://code.djangoproject.com/ticket/8340#comment:6>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
