#9682: icontains can be case-sensitive on MySQL
-----------------------------------------------------+----------------------
Reporter: [email protected] | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------+----------------------
Comment (by mykhal):
I strongly vote for this. It solves the problem how to insert "COLLATE
<collation>" into the query, invoked by normal filters (without writing
SQL from scratch).
Why would one need to use COLLATE? E.g. in case, when he has a database
containing strings with accented characters, and this database is in the
different collation than utf8_general_ci - e.g. utf8_czech_ci. In this
case, sql select e.g. "{{{SELECT ... LIKE %cviceni% ...}}}" does not hit
strings containing "cvičení", but it does, when "{{{SELECT ... COLLATE
utf8_general_ci LIKE %cviceni% ...}}}" . What is interesting, if {{{ORDER
BY}}} is used, results are ordered by the original database collation
(czech in this case), what might be exactly what he needs.
--
Ticket URL: <http://code.djangoproject.com/ticket/9682#comment:5>
Django <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
-~----------~----~----~----~------~----~------~--~---
