| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Thomas Swan <tswan(at)olemiss(dot)edu>, Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LIKE/ESCAPE implementation |
| Date: | 2000-08-06 04:10:10 |
| Message-ID: | 23112.965535010@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> I had thought it would be trivial to do ILIKE, but now I'm not sure how
> to handle the multi-byte case. It isn't sufficient to wrap the
> single-byte comparison arguments with tolower() is it??
I'd be inclined to force both strings to lower case as a whole and
then apply normal LIKE. Comments anyone?
> I recall people asking for it, but since it is a non-standard
> feature what implementation example should I follow? What alternatives
> are there? Is "check the archives" sufficient to produce a complete
> design discussion?
I do not recall seeing a complete proposal, but wasn't someone just
opining that Oracle has such a feature? If so, borrowing their spec
seems the thing to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-08-06 04:12:38 | Re: COALESCE implementation question |
| Previous Message | Thomas Lockhart | 2000-08-06 03:45:57 | Re: LIKE/ESCAPE implementation |