Message-ID: <20030623032929.28505.qmail@celery.tssi.com>
From: nolan@celery.tssi.com
Subject: Re: [GENERAL] interesting PHP/MySQL thread
To: scrappy@postgresql.org (The Hermit Hacker)
Date: Sun, 22 Jun 2003 22:29:29 -0500 (CDT)
Cc: JanWieck@Yahoo.com (Jan Wieck), pgman@candle.pha.pa.us (Bruce Momjian),
	josh@agliodbs.com (Josh Berkus), mail@joeconway.com (Joe Conway),
	pgsql-advocacy@postgresql.org (\"\"Advocacy PostgreSQL\"\"),
	pgsql-general@postgresql.org (PostgreSQL-general)
In-Reply-To: <20030623000257.X95856@hub.org> from "The Hermit Hacker" at Jun
	23, 2003 12:03:18 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> On Sun, 22 Jun 2003 nolan@celery.tssi.com wrote:
> 
> > MySQL also does case independent text comparisions, and apparently ONLY
> > case-insensitive comparisons.
> 
> Is this a good thing?  Doesn't sound like it to me, but figured I'd ask :)

I think it is a classic case of thinking 'small'.  :-)

The CIO on the project I'm working on thinks it is a good thing,
but he's coming from a MySQL environment, which he only learned in the
last year or so and he does not appear to have a lot of familiarity with
larger databases.   

Personally, if I want case insensitivity, I'll WRITE IT INTO THE CODE,
but I can see how some people might think that 'NOLAN', 'Nolan' and 
'nolan' should be considered as the same data.  

BTW, I just tested it and MySQL does case folding on values in unique 
indexes, too.  (Well, at least it is consistent.)
--
Mike Nolan