Message-ID: <3EF725CA.2060508@cvc.net>
Date: Mon, 23 Jun 2003 09:07:38 -0700
From: Dennis Gearon <gearond@cvc.net>
Reply-To: gearond@cvc.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.4b) Gecko/20030507
MIME-Version: 1.0
To: nolan@celery.tssi.com
Cc: The Hermit Hacker <scrappy@postgresql.org>,
 Jan Wieck <JanWieck@Yahoo.com>,
	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: <20030623053352.1457.qmail@celery.tssi.com>
In-Reply-To: <20030623053352.1457.qmail@celery.tssi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Looks like there's some parts of that that would make a good todo.

nolan@celery.tssi.com wrote:

>>>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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
>                http://archives.postgresql.org
>