List:General Discussion« Previous MessageNext Message »
From:Martin Ramsch Date:September 17 1999 5:57pm
Subject:Re: case insensitive? not for me.
View as plain text  
On Thu, 1999-09-16 04:37:41 -0700, Mark Maggelet wrote:
> all the documentation I've read says that a select on a varchar is
> case insensitive, so who do
> 
> select * from person where locate("James",firstname)<>0
> 
> and
> 
> select * from person where locate("james",firstname)<>0
> 
> give me different results? (the first finds 'James', the second
> doesn't)

A 'select' can't be case sensitive or insensitive, only comparisons or
functions on which a select is based.

And that's it:
  =     (the normal comparison with equal sign) is normally case
        insensitive
  LIKE  is normally case insensitive

All the other string functions are case sensitive, as is the REGEXP or
RLIKE operator.

Both = and LIKE act case sensitive on columns defined BINARY.

Regards,
  Martin
-- 
Martin Ramsch <m.ramsch@stripped> <URL: http://home.pages.de/~ramsch/ >
PGP KeyID=0xE8EF4F75 FiPr=52 44 5E F3 B0 B1 38 26  E4 EC 80 58 7B 31 3A D7
Thread
case insensitive? not for me.Mark Maggelet16 Sep
  • Re: case insensitive? not for me.James Manning17 Sep
  • Re: case insensitive? not for me.Martin Ramsch17 Sep