Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by postgresql.org (Postfix) with ESMTP
	id 27920474E6D; Wed, 24 Jul 2002 22:27:09 -0400 (EDT)
Received: from [66.219.92.2] (HELO chocolate-mousse)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9)
	with ESMTP id 1589203; Wed, 24 Jul 2002 19:27:12 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>,
	"Carmen Wai" <wai_carmen@hotmail.com>, <pgsql-sql@postgresql.org>,
	<pgsql-general@postgresql.org>
Subject: Re: [SQL] Case in-sensitive
Date: Wed, 24 Jul 2002 19:27:42 -0700
X-Mailer: KMail [version 1.4]
References: <GNELIHDDFBOCMGBFGEFOAEFFCDAA.chriskl@familyhealth.com.au>
In-Reply-To: <GNELIHDDFBOCMGBFGEFOAEFFCDAA.chriskl@familyhealth.com.au>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200207241927.42145.josh@agliodbs.com>
X-Archive-Number: 200207/1515
X-Sequence-Number: 28002

Chris,

> > Can I config the Postgresql so that it can match case
> > in-sensitive pattern
> > automatically? i.e. I don't need to explicit convert the pattern to low=
er
> > case like this: .....WHERE lower(textfield) LIKE lower(pattern)
>=20
> All you need to do is this:
>=20
> ......WHERE textfield ILIKE pattern

Though, keep in mind, lower(textfield) can be indexed, but ILIKE textfield=
=20
cannot.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco