Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2J3Av655053 for ; Sun, 18 Mar 2001 22:10:57 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2J3Att03016; Sun, 18 Mar 2001 22:10:55 -0500 (EST) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: What do I do with this error? In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Sun, 18 Mar 2001 17:39:53 -0800" Date: Sun, 18 Mar 2001 22:10:55 -0500 Message-ID: <3013.984971455@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/346 X-Sequence-Number: 2010 "Josh Berkus" writes: > Never mind. It turns out that if you call try to feed a NULL to a > regular expression (e.g. Client_name ~* NULL) you get: > ERROR: regcomp failed with error empty (sub)expression > Good to know. I had expected that regular expressions, like other > operators, would return NULL if NULL was the pattern. Is this a bug? Yes, I'd say so. 7.1 returns a NULL as expected ... regards, tom lane