On Thu, 2008-10-16 at 11:15 -0700, AndyB wrote: > Well - someone on #Django told me to check encoding settings and I did > but I failed to read the following: > http://dev.mysql.com/doc/refman/5.0/en/case-sensitivity.html > > Using binary collation changes the default sensitivity of string > comparisons. > > Is this not something that Django should be abstracting away?
No. You set the database collation and Django respects that. We can't do anything else, since the comparison takes place at the database level. The other one is that we (particularly Karen Tracey, myself and a couple of other people) spent a lot of time trying to see if we could make things like that work regardless of collation (particularly case-sensitive matching with the default utf_*_ci collations), but it's really, really hard. Really hard. There are just too many side-effects and, ultimately, it becomes hard to understand what's going on in a practical matter, since we almost always defer to the database on matters on how a particular SQL query will be executed and this would be one situation when we didn't (sometimes). So it's entirely left up to how you configure your database. One of the trade-offs the developer chooses to make when selecting MySQL. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
