Closed (won't fix)
Project:
Project issue tracking
Version:
5.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2007 at 16:12 UTC
Updated:
10 Mar 2012 at 18:03 UTC
originally reported at http://drupal.org/node/189278 -- which has moved to a separate issue.
this is a bit of a rat's nest. here's what i've found so far:
it looks to me like the simplest solution is to use the postgres custom ILIKE operator for these searches, in the case where postgres is the database. we could try using the 'lower' function here in all cases, but i'm not sure of the performance implications, and i'm also not sure it's implementation is consistent across databases.
attached patch uses the ILIKE approach.
| Comment | File | Size | Author |
|---|---|---|---|
| search_case.patch | 927 bytes | hunmonk |
Comments
Comment #1
dwwI believe we should wait and see what the big kids come up with over at http://drupal.org/node/83738 before we take any action here. There's *a lot* of interest and expertise in the exact same problem, but for core itself, and I think we should stand on the shoulders of giants whenever possible.
That said, one of the options under consideration is a pgsql-specific ILIKE, just like you've got here, so this might end up being the patch we commit, anyway. ;)
Thanks,
-Derek
Comment #2
Kjartan commentedIn 6.x the search is completely redone, and from what I can tell this isn't an issue any more.
The fix for the similar issue in core was to use ILIKE so the original patch would probably be the proper fix should anyone run into this in 5.x.