Thanks, both done. ---------------------------------------------------------------------------
Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > Tom Lane wrote: > >> So yeah, ILIKE looks just about completely broken for multibyte encodings. > > > Did we make any progress on this? If so, I can't find it. > > No, nobody submitted a patch AFAIR. There should be a TODO item for > this: > > * fix ILIKE and regular expressions to handle case insensitivity > properly in multibyte encodings > > BTW, while looking to see if TODO had anything about this, I noted > the following items that shouldn't be there anymore --- they are > done and pushed out: > > o Add new version of PQescapeString() that doesn't double backslashes > that are part of a client-only multibyte sequence > > Single-quote is not a valid byte in any supported client-only > encoding. This requires using mblen() to determine if the > backslash is inside or outside a multi-byte sequence. > > o Add new version of PQescapeString() that doesn't double > backslashes when standard_conforming_strings is true and > non-E strings are used > > > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
