Date: Tue, 10 Feb 2004 11:04:55 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-general@postgresql.org
Subject: Re: Case sensitivity
Message-ID: <20040210160455.GB28540@phlogiston.dyndns.org>
Mail-Followup-To: pgsql-general@postgresql.org
References: <04875CB4331F0240A0AD66F970978651011377D5@paul>
	<4028740F.7000104@zara.6.isreserved.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4028740F.7000104@zara.6.isreserved.com>
User-Agent: Mutt/1.5.4i

On Tue, Feb 10, 2004 at 01:02:55PM +0700, David Garamond wrote:
> 
> I believe no. You can index on LOWER(f) or UPPER(f) but that still 
> requires a query rewriting to WHERE LOWER(f) = .... You can also write 
> INSERT triggers to convert values to upper case, but that still requires 
> query rewriting if you're comparing with mixed-case values.

But you could do some tricks with rules (plus the indexes and
triggers you mentioned) in order to lower() or upper() the input, if
you happen to know where you're likely to have the problems.

It's certainly true, however, that from the point of view of keeping
your data clean, you want these steps handled before the data
actually gets into the database.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The plural of anecdote is not data.
		--Roger Brinner