Received: from biology.nmsu.edu (biology.NMSU.Edu [128.123.5.72]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA78337 for ; Wed, 17 May 2000 17:01:36 -0400 (EDT) (envelope-from brook@biology.nmsu.edu) Received: (from brook@localhost) by biology.nmsu.edu (8.8.8/8.8.8) id PAA21328; Wed, 17 May 2000 15:01:35 -0600 (MDT) Date: Wed, 17 May 2000 15:01:35 -0600 (MDT) Message-Id: <200005172101.PAA21328@biology.nmsu.edu> X-Authentication-Warning: biology.nmsu.edu: brook set sender to brook@biology.nmsu.edu using -f From: Brook Milligan To: kyle@actarg.com CC: pgsql-sql@postgresql.org In-reply-to: <39230546.62BE1AD9@actarg.com> (message from Kyle Bateman on Wed, 17 May 2000 14:47:02 -0600) Subject: Re: question on update/delete rules on views References: <3921E506.82424CAF@actarg.com> <200005171352.HAA19867@biology.nmsu.edu> <3922B7A2.5BEF5F5E@actarg.com> <200005171751.LAA20341@biology.nmsu.edu> <39230546.62BE1AD9@actarg.com> X-Archive-Number: 200005/37 BTW, do you have an equally sensible explanation of how the "where condition" that is part of the rule syntax differs from the where clause that comes after the "do instead"? I don't know what you mean by these two different where conditions. To my understanding the only instance of a where condition in the rule is in the "do" part. Think of triggering the "do" part individually for each view tuple to be updated. If you wish to act on a table, you must identify how the parts of the current tuple identify a tuple or tuples in the target table. That is the sole role of the "where" condition in the "do" part of the rule. Cheers, Brook