Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 45AAC4764ED for ; Thu, 13 Jun 2002 00:38:44 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 630CD47671C for ; Thu, 13 Jun 2002 00:35:13 -0400 (EDT) Received: from [63.195.55.98] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1525843; Wed, 12 Jun 2002 21:35:15 -0700 From: "Josh Berkus" Subject: Re: Case insensitive select To: "isaac flemmin" , "'Stephan Szabo'" Cc: X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Wed, 12 Jun 2002 21:35:15 -0700 Message-ID: In-Reply-To: <000001c2127e$df411980$ad463e04@ixic> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200206/163 X-Sequence-Number: 8128 Isaac, > Yes that worked. Thanks! I will have to look more at the lower > function > now so I know why that worked! It has nothing to do with the LOWER function, which is straigthforward. You made the beginner's mistake of defining your column as CHAR and not VARCHAR. As a result, what is actually being stored in your database is not: "Value" "Value1" but: "Value " "Value1 " This is what is causing your search problems. Dump the table, and re-build it with the correct data types (VARCHAR!). I would also strongly reccomend that you pick up a beginner's book on SQL database building. See: http://techdocs.postgresql.org/techdocs/bookreviews.php Also, unlike most other RDBMS, CHAR is *not* more efficient than VARCHAR in Postgres. -Josh Berkus