Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7E6fYP61026 for ; Tue, 14 Aug 2001 02:41:34 -0400 (EDT) (envelope-from njclark@ntsp.nec.co.jp) Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO202.gate.nec.co.jp (8.11.3/3.7W01080315) with ESMTP id f7E6fM129562; Tue, 14 Aug 2001 15:41:22 +0900 (JST) Received: from fireball.ntsp.nec.co.jp (mailgate51.nec.co.jp [10.7.69.190]) by mailgate4.nec.co.jp (8.11.3/3.7W-MAILGATE-NEC) with ESMTP id f7E6fE114059; Tue, 14 Aug 2001 15:41:15 +0900 (JST) Received: (from smtp@localhost) by fireball.ntsp.nec.co.jp (8.9.2/8.9.2) id OAA09051; Tue, 14 Aug 2001 14:39:26 +0800 (HKT) Received: from UNKNOWN(172.28.58.129), claiming to be "avalon.ntsp.nec.co.jp" via SMTP by fireball.ntsp.nec.co.jp, id smtpdAAA0U91n5; Tue Aug 14 06:39:17 2001 Received: from ntsp.nec.co.jp ([172.28.59.157]) by avalon.ntsp.nec.co.jp (8.9.2/8.9.2) with ESMTP id OAA06579; Tue, 14 Aug 2001 14:36:50 +0800 (HKT) Message-ID: <3B78C966.4FC8F6CC@ntsp.nec.co.jp> Date: Tue, 14 Aug 2001 14:47:03 +0800 From: John Clark Naldoza y Lopez Organization: NEC Telecom Software X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-20mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: scott.gilbert@netregistry.au.com CC: pgsql-general@postgresql.org Subject: Re: Case sensitivity References: Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/328 X-Sequence-Number: 13572 Hello Scott, PostgreSQL also supports regular expressions, _VERY_ useful..;-) ~* regular expression, case-insensitive..;-) Try to get a copy of Bruce's book Introduction and Concepts by Bruce Momjian A sample from the book: SELECT * FROM friend WHERE firstname ~* '[bc]' read it online, or just read the docs online...;-) http://techdocs.postgresql.org Cheers, John Clark p.s. don't change PostgreSQL, change your SQL statements...;-) Scott Gilbert wrote: > > We intend to move from M$ Access to PostgreSQL, however, much of our legacy > code operates under the assumption that string or text comparisons are case > insensitive whereas postgres is case sensitive. This issue extends to SQL > Select statements as well as straight comparison (i.e. in addition to the <, > > and = operators, the WHERE and IN clauses in SQL statements are also > issues) so we can't simply modify the function attached to the comparison > operators. Is there some means of modifying the behaviour of PostgreSQL so > that it is case insensitive? -- /) John Clark Naldoza y Lopez (\ / ) Software Design Engineer III ( \ _( (_ _ Web-Application Development _) )_ (((\ \> /_> Cable Modem Network Management System <_\