#8877: Very strange bug in MySQL backend for exact query.
-------------------------------------+--------------------------------------
Reporter: bear330 | Owner: nobody
Status: closed | Milestone:
Component: Core framework | Version: 1.0
Resolution: invalid | Keywords: get exact SQL ORM MySQL
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by kmtracey):
Replying to [comment:1 russellm]:
> If you don't want case insensitive field comparisons, you need to set up
your MySQL install to use a different collation.
And you'll want to be sure to read:
http://docs.djangoproject.com/en/dev/ref/databases/#mysql-collation to
avoid getting hit by a known gothca resulting from using a binary
collation. Also it's not noted there (but is somewhere in the MySQL doc
pointed to), but using a binary collation will change the ordering
results. The default case-insensitive collation give dictionary ordering
(a, A, z, Z) whereas binary collation gives binary ordering (A, Z, a, z).
--
Ticket URL: <http://code.djangoproject.com/ticket/8877#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
