#8340: MySQL case sensitivity and utf8_bin / 2710
------------------------------------+---------------------------------------
Reporter: hrauch | Owner: zbskii
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 mtredinnick):
After extensive investigations from Karen and zbskii (who spent a whole
day on this at the Portland sprint) and some checking from me, this is
Officially Hard(tm). We can't really make things work correctly in all
cases without harming people using `VARBINARY` fields (which is simply not
an option).
Thus, this is going to be documented as a "trap" for 1.0. I will fix the
session backend to handle this situation (which was the original bug
reported here) and anybody else discovering this problem in Django core
code can open new tickets. People will just have to work around it in
their own code (with judicious calls to `force_unicode()`) if they want to
operate in this mode.
The commit to the session backend will close this ticket. I'll update the
docs once Jacob lands the docs refactor in the next 24 hours or so (we
have a temporary freeze on docs changes at the moment).
--
Ticket URL: <http://code.djangoproject.com/ticket/8340#comment:9>
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
-~----------~----~----~----~------~----~------~--~---
