If a patch is needed, would a new operator "ilike" be okay?
>Maybe I'm not understanding this. Is ILIKE only a mysql thing? So is
>LIKE normally case insensitive in complaint SQL database?
>
>
ILIKE is quasi-standard. Postgres has it as well, but MSSQL doesn't -
all LIKEs (and in equals too in fact) are case insensitive.
Paul
creating indexes on lower(col) would speed that up.
Andreas
* Paul Kippes <paul.want...@gmail.com> [070404 20:07]:
The key word ILIKE can be used instead of LIKE to make the match
case-insensitive according to the active locale. This is not in the
SQL standard but is a PostgreSQL extension.
http://www.postgresql.org/docs/current/static/functions-matching.html#FUNCTIONS-LIKE
Andreas
there is also a general notion of "case sensitive compare"/"case
insensitive compare". we have a rather involved way to solve this
which is talked about in ticket #487, including a PG patch. the
ultimate ability is to put a flag on Column
"case_insensitive_compares" that would produce a DB-specific "case
insensitive" comparison operation automatically. but complicating
matters is MySQL where compares are *already* case insensitive unless
you play around with their non-SQL COLLATE expression. something
that should be looked about/thought about with regards to this matter.