Message-ID: <20030623053352.1457.qmail@celery.tssi.com>
From: nolan@celery.tssi.com
Subject: Re: [GENERAL] interesting PHP/MySQL thread
To: scrappy@postgresql.org (The Hermit Hacker)
Date: Mon, 23 Jun 2003 00:33:51 -0500 (CDT)
Cc: scrappy@postgresql.org (The Hermit Hacker),
 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: <20030623015333.E95856@hub.org> from "The Hermit Hacker" at Jun
	23, 2003 01:54:24 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> > 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.
> 
> 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. 

Also, unlike PostgreSQL (at least in 7.3), if you define an index on
the column, mysql appears to use it for LIKE queries.

   "SELECT * FROM table WHERE field LIKE 'nolan%';" 

is very fast in mysql but not in 7.3, and even non-anchored LIKE searches
in mysql appear to be using the index.
  
   "SELECT * FROM table WHERE field LIKE '%nolan%';" 

executes considerably faster with an index on field than without one.
--
Mike Nolan