| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 03:45:57 |
| Message-ID: | 398CDF75.73126950@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > What is ILIKE? afaik it is not in SQL9x, so is there any reason to have
> > that rather than the full regular expression case-insensitive operator
> > ("~*") we already have?
> Just that a lot of people have asked for it, over and over again ...
> see the archives ...
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??
btw, do the archives have a full discussion of the correct syntax for
this? 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? What thread??
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-06 04:10:10 | Re: LIKE/ESCAPE implementation |
| Previous Message | Tom Lane | 2000-08-06 03:28:08 | Re: COALESCE implementation question |