Re: tolower() identifier downcasing versus multibyte encodings - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: tolower() identifier downcasing versus multibyte encodings
Date
Msg-id AANLkTik9q78ziWT3_71QyokJGqtCyUHPqZRewmEX1d7L@mail.gmail.com
Whole thread Raw
In response to tolower() identifier downcasing versus multibyte encodings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tolower() identifier downcasing versus multibyte encodings
List pgsql-hackers
On Sat, Mar 19, 2011 at 6:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Or we could bite the bullet and start using str_tolower(), but the
> performance implications of that are unpleasant; not to mention that
> we really don't want to re-introduce the "Turkish problem" with
> unexpected handling of i/I in identifiers.

How about first pass with 'a' - 'A' and if highbit is found
then str_tolower()?

You will still confuse turks, but at least nothing should break.

-- 
marko


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: tolower() identifier downcasing versus multibyte encodings
Next
From: Magnus Hagander
Date:
Subject: Re: Indent authentication overloading