| From: | Andrew - Supernews <andrew+nonews(at)supernews(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: like/ilike improvements |
| Date: | 2007-05-22 17:40:36 |
| Message-ID: | slrnf56aok.2v2f.andrew+nonews@atlantis.supernews.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On 2007-05-22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If "%" advances by bytes then this will find a spurious match. The
> only thing that prevents it is if "B" can't be both a leading and a
> trailing byte of validly-encoded MB characters.
Which is (by design) true in UTF8, but is not true of most other
multibyte charsets.
The %_ case is also trivially handled in UTF8 by simply ensuring that
_ doesn't match a non-initial octet. This allows % to advance by bytes
without danger of losing sync.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mark | 2007-05-22 18:44:25 | Re: like/ilike improvements |
| Previous Message | Guillaume Smet | 2007-05-22 17:38:48 | Re: like/ilike improvements |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mark | 2007-05-22 18:44:25 | Re: like/ilike improvements |
| Previous Message | Guillaume Smet | 2007-05-22 17:38:48 | Re: like/ilike improvements |