#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 |
-------------------------------------+--------------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
This isn't a bug in Django. It's a problem with MySQL - or at least, with
with way your MySQL server is configured.
Your MySQL installation is set up to use a text field collation that is
case insensitive. In the alpha/beta series, we briefly toyed with working
around this issue, but it turned out to cause more problems than it
solved.
If you don't want case insensitive field comparisons, you need to set up
your MySQL install to use a different collation.
--
Ticket URL: <http://code.djangoproject.com/ticket/8877#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
