Re: like/ilike improvements
От
Andrew - Supernews
Тема
Re: like/ilike improvements
Дата
Msg-id
slrnf56aok.2v2f.andrew+nonews@atlantis.supernews.net
Список
Дерево обсуждения
Re: like/ilike improvements Andrew - Supernews <andrew+nonews@supernews.com>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements mark@mark.mielke.cc
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements "Zeugswetter Andreas ADI SD" <ZeugswetterA@spardat.at>
Re: like/ilike improvements Andrew Dunstan <andrew@dunslane.net>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
Re: like/ilike improvements Tom Lane <tgl@sss.pgh.pa.us>
On 2007-05-22, Tom Lane 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
В списке pgsql-hackers по дате отправления