> select * from table where field ILIKE 'blAH';  -- ;-)
> is almost as easy :-)
> PS: no, don't do this if you want portability. I think the charset
> idea's a better one.
>
> Ron

���select * from table where lower(field)=lower('BLah')��� will break
portability too in the sense that many DBs (perhaps all commercial
ones) do not support functional indexes. Hence
���lower(field)=lower('BLah')��� query will not be using index when it runs
on those DBs.

Besides, the developer must always remember to use conversion when
writing queries. This does not sound bad initially but in a big
application with many developers and complex query logic this will
create quite a few annoying, time consuming and difficult to find bugs.

Case insensitive charset definitely sounds like a better idea. Has
anyone done this yet? IMHO, this should be a part of core distribution
since 99.999999% of queries do not need case sensitivity.

Thanks


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com


Sun, 23 Mar 2003 05:21:19 -0800 (PST)
ow <oneway_111@yahoo.com>
Re: Case insensitivity, and option?