On Tue, Jun 8, 2010 at 10:00 AM, Tom Evans <tevans...@googlemail.com> wrote:
> This may have other unintended side effects, certainly it will make > the match case sensitive, I'm not sure if __exact is supposed to be > case sensitive. > Yes, it will have side-effects, bad enough that it's not worth doing. It was once done, so as to make the exact comparison case-sensitive like the other Django-supported DBs: http://code.djangoproject.com/changeset/7798 and eventually reverted: http://code.djangoproject.com/changeset/8319 after considerable debate and investigation into possible ways to make __exact on MySQL behave more like other Django DBs. In the end (at least for now) the solution is to document that the results for comparisons on MySQL are governed by the MySQL collation setting: http://docs.djangoproject.com/en/dev/ref/databases/#collation-settings. 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 django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
