"Zeugswetter Andreas ADI SD" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq