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

Re: BUG #1931: ILIKE and LIKE fails on Turkish locale

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Devrim GUNDUZ <devrim(at)gunduz(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1931: ILIKE and LIKE fails on Turkish locale
Date: 2006-06-14 21:33:49
Message-ID: 3964.1150320829@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-tr-genel
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

pgsql-tr-genel by date

Next:From: Bruce MomjianDate: 2006-06-14 21:40:05
Subject: Re: BUG #1931: ILIKE and LIKE fails on Turkish locale
Previous:From: Bruce MomjianDate: 2006-06-14 21:00:13
Subject: Re: BUG #1931: ILIKE and LIKE fails on Turkish locale

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2006-06-14 21:40:05
Subject: Re: BUG #1931: ILIKE and LIKE fails on Turkish locale
Previous:From: Bruce MomjianDate: 2006-06-14 21:10:58
Subject: Re: BUG #1937: Parts of information_schema only accessible

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group