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

Re: tolower() identifier downcasing versus multibyte encodings

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, "Francisco Figueiredo Jr(dot)" <francisco(at)npgsql(dot)org>
Subject: Re: tolower() identifier downcasing versus multibyte encodings
Date: 2011-03-19 09:25:05
Message-ID: AANLkTik9q78ziWT3_71QyokJGqtCyUHPqZRewmEX1d7L@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, Mar 19, 2011 at 6:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2011-03-19 13:14:18
Subject: Re: Indent authentication overloading
Previous:From: Dave PageDate: 2011-03-19 07:08:06
Subject: Re: pgsql: Document the all-balls IPv6 address.

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