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 f0P4rjq07891 for ; Wed, 24 Jan 2001 23:53:45 -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 f0P4rT926491; Wed, 24 Jan 2001 23:53:29 -0500 (EST) To: Kyle cc: pgsql-sql@postgresql.org Subject: Re: Rule not invoked in 7.1 In-reply-to: <3A6F53C8.CA9FE05C@actarg.com> References: <3A6F53C8.CA9FE05C@actarg.com> Comments: In-reply-to Kyle message dated "Wed, 24 Jan 2001 15:14:32 -0700" Date: Wed, 24 Jan 2001 23:53:29 -0500 Message-ID: <26488.980398409@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/348 X-Sequence-Number: 1021 Kyle writes: > ERROR: Cannot update a view without an appropriate rule. 7.1 insists that you provide an *unconditional* DO INSTEAD rule for a view. What do you think was happening on your old database when the "where old.status = 'appr'" clause wasn't satisfied? Nothing good I'm afraid. If you really do need conditional rules, you can satisfy the check by writing one unconditional DO INSTEAD NOTHING rule and then one or more conditional non-INSTEAD rules. But you should think carefully about what you expect to happen when you use a conditional rule. regards, tom lane