From: Ian Barwick <barwick@gmx.net>
To: nolan@celery.tssi.com, scrappy@postgresql.org (The Hermit Hacker)
Subject: Re: [GENERAL] interesting PHP/MySQL thread
Date: Mon, 23 Jun 2003 10:01:20 +0200
User-Agent: KMail/1.5.1
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)
References: <20030623053352.1457.qmail@celery.tssi.com>
In-Reply-To: <20030623053352.1457.qmail@celery.tssi.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306231001.20653.barwick@gmx.net>

On Monday 23 June 2003 07:33, 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';"

bad memories ... of website login system ... using MySQL ... returning
several results for a unique login / pw combination ...

To stop this behaviour in MySQL one needs to define CHAR and VARCHAR types
with a "BINARY" attribute, e.g.:

  CREATE TABLE tbl (field VARCHAR(24) BINARY)

My fault though for not reading the manual attentively enough ;-).
-> http://www.mysql.com/doc/en/CHAR.html


Ian Barwick
barwick@gmx.net