Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: like/ilike improvements


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
  • Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: like/ilike improvements
  • Date: Fri, 25 May 2007 09:42:18 -0400
  • Message-id: <8094(dot)1180100538(at)sss(dot)pgh(dot)pa(dot)us>

"Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at> writes:
>> 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).

> Well, for utf8 NextChar could advance to the next char even if the
> current byte
> position is in the middle of a multibyte char (skip over all 10xxxxxx). 

No doubt the macro could be made to work that way, but would it result
in correct matching behavior?  I doubt it --- you just matched an "_"
to half a character, or some such.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group