Received: from antares.mcs.anl.gov (mcs.anl.gov [140.221.9.6]) by hub.org (8.8.8/8.7.5) with SMTP id LAA09728 for ; Wed, 20 May 1998 11:49:13 -0400 (EDT) Received: from mcs.anl.gov ([195.19.5.5]) by antares.mcs.anl.gov (8.6.10/8.6.10) with ESMTP id KAA17999; Wed, 20 May 1998 10:48:46 -0500 Sender: selkovjr@mcs.anl.gov Message-ID: <3562FAFE.185F242D@mcs.anl.gov> Date: Wed, 20 May 1998 15:47:10 +0000 From: "Eugene Selkov Jr." X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.32 i586) MIME-Version: 1.0 To: Jerome Knobl CC: Mike Lemler , pgsql-sql@postgreSQL.org Subject: Re: [SQL] Case in-sensitive searches References: <3.0.5.32.19980518160401.007bd330@datacruz.com> <35612DDB.6A86EDA3@mandanet.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jerome Knobl wrote: > > Hi, > > I found an inellegant sollution. You can put every character in uppercase > like that : > > Select * From table_membres where upper(nom) like upper('myname'); > I use a much less elegant solution that works extremely well for me. I add a copy of the column to the table and fold it uppercase before I load the table. I also do some additional processing in it, in order to eliminate things that may interfere with indexing, such as accents in European characters. The application then decides whether to search in the original or in the processed copy of the column, but the original data are always returned to the user. --Gene