Re: Stopgap solution for ILIKE in multibyte encodings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stopgap solution for ILIKE in multibyte encodings
Date: 2006-09-04 18:38:57
Message-ID: 10386.1157395137@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> writes:
> On 9/4/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I propose that for ILIKE in multibyte encodings, we just pass the strings
>> through lower() and then use the normal LIKE code.

> Perhaps it's a stupid question but what about the indexes? An index on
> lower(field) will be used by the new code or we wiil keep the current
> behaviour of ILIKE?

No, this is just an internal change in the function's implementation,
it won't have any effect like that. If you want indexing you'd still
need to write out "lower(col) like whatever".

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2006-09-04 18:42:21 Re: [PATCHES] Contrib module to examine client
Previous Message Dennis Bjorklund 2006-09-04 18:30:27 setseed() doc