On Tue, Jun 8, 2010 at 12:55 PM, zayatzz <[email protected]> wrote:
> > > > The need to do this when using a binary collation with MySQL is > documented: > http://docs.djangoproject.com/en/dev/ref/databases/#collation-settings. If > > in fact this is necessary in some circumstances even when using a > non-binary > > collation I'd like to understand that -- but in my testing the only way I > > can get behavior like what you are seeing is when I set the collation to > a > > binary one. > > > Well. It's like you said. If i create the database with swedish_ci, > then it works just fine. Unless you have a really pressing need for case-sensitive __exact comparisons, I'd recommend using a non-binary collation on MySQL. (And if you have such a need, I'd think about perhaps using a different database...the character-data-coming-back-as-bytestring-instead-of-unicode behavior with MySQL and a binary collation is just something I personally would not want to code around.) > Looks like i have gaps in my education, but > since i dont know where they are i just learn when i stumble upon > problems. The link you posted about collation settings taught me alot > so if i look at the things from my self interest prespective, i cant > see the fault in posting this question. Although to you probably it > looks like wasted time :). > No, if you've learned something it's not wasted time. That's why I read and respond to questions here. Karen -- http://tracey.org/kmt/ -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
