Message-ID: <3EF6F0D8.9070408@Yahoo.com>
Date: Mon, 23 Jun 2003 08:21:44 -0400
From: Jan Wieck <JanWieck@Yahoo.com>
Organization: Unorganized
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.2) Gecko/20030208 Netscape/7.02
MIME-Version: 1.0
To: Lincoln Yeoh <lyeoh@pop.jaring.my>
Cc: nolan@celery.tssi.com, The Hermit Hacker <scrappy@postgresql.org>,
	Bruce Momjian <pgman@candle.pha.pa.us>,
	Josh Berkus <josh@agliodbs.com>, Joe Conway <mail@joeconway.com>,
	Advocacy PostgreSQL <pgsql-advocacy@postgresql.org>,
	PostgreSQL-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] interesting PHP/MySQL thread
References: <20030623015333.E95856@hub.org>
	<5.2.1.1.1.20030623221452.02f7fd48@mbox.jaring.my>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Lincoln Yeoh wrote:
> At 12:33 AM 6/23/2003 -0500, nolan@celery.tssi.com wrote:
>> >
>> > Oh, you mean like "SELECT * FROM table WHERE field ~* 'nolan';"?
>>
>>No, I mean as in "SELECT * FROM table WHERE field = 'nolan';"
>>
>>That will match values with any combination of upper and lower case
>>letters that fold to 'nolan':  'Nolan', 'NOLAN', etc.
> 
> For me that's a matter of taste. I prefer to use = for case sensitive and 
> lower(field)=lower('data') for case insensitive. I wonder if there is a 
> difference between using lower vs upper for case insensitivity but I've 
> never bothered to look deeply into it.

In some character sets there might be. The German sz-ligature for 
example has no upper case equivalent, and in turkish the upper cases of 
i and y with two dots are exchanged.

I prefer your example too and since we have functional indexes, it 
doesn't affect performance at all.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #