Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id B825B476049; Fri, 22 Feb 2002 15:20:49 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g1MKKdS19466; Fri, 22 Feb 2002 15:20:39 -0500 (EST) To: Fernando Schapachnik Cc: "Samuel J. Sutjiono" , pgsql-sql@postgresql.org, pgsql-general@postgresql.org Subject: Re: Regular Expression for 'and' instead of 'or' In-reply-to: <20020222151514.E2066@ns1.via-net-works.net.ar> References: <023101c1bbc3$03a33910$110a010a@headquarters.wcgroup.com> <20020222151514.E2066@ns1.via-net-works.net.ar> Comments: In-reply-to Fernando Schapachnik message dated "Fri, 22 Feb 2002 15:15:14 -0300" Date: Fri, 22 Feb 2002 15:20:39 -0500 Message-ID: <19463.1014409239@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/1078 X-Sequence-Number: 21074 Fernando Schapachnik writes: > You have to use something like: > '(socks.*shoes.*nike)|(socks.*nike.*shoes)|...' > where ... is every other possible combination. Not pretty, but that's > a limitation of finite automata (or regular expressions, which are > the same). Seems a lot easier to do WHERE field ~* 'socks' AND field ~* 'shoes' AND field ~* 'nike' regards, tom lane