| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: like/ilike improvements |
| Date: | 2007-05-25 02:03:42 |
| Message-ID: | 29235.1180058622@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> You have to be on a first byte before you can meaningfully apply
>> NextChar, and you have to use NextChar or else you don't count
>> characters correctly (eg "__" must match 2 chars not 2 bytes).
> Yes, I agree completely. However it looks to me like IsFirstByte will in
> fact always be true when we get to call NextChar for matching "_" for UTF8.
If that's true, the patch is failing to achieve its goal of treating %
bytewise ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guido Barosio | 2007-05-25 02:11:49 | block size |
| Previous Message | Andrew Dunstan | 2007-05-25 01:56:58 | Re: like/ilike improvements |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-05-25 03:20:51 | Re: like/ilike improvements |
| Previous Message | Andrew Dunstan | 2007-05-25 01:56:58 | Re: like/ilike improvements |