Re: question on update/delete rules on views

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kyle Bateman <kyle(at)actarg(dot)com>
Cc: Brook Milligan <brook(at)biology(dot)nmsu(dot)edu>, pgsql-sql(at)postgresql(dot)org
Subject: Re: question on update/delete rules on views
Date: 2000-05-17 21:47:13
Message-ID: 18953.958600033@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Kyle Bateman <kyle(at)actarg(dot)com> writes:
> 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"?

The rule WHERE condition determines *whether* the rule is fired for
update of a given view tuple. (If it isn't, then that tuple is
processed as if there were no rule.) Assuming that the rule fires,
a WHERE inside its action will determine which tuples it actually
acts on.

I think there are some examples in the docs of uses of nonempty rule
WHERE conditions. If not, you could try looking at the rules regression
test for examples ...

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Daniel Mendyke 2000-05-18 00:52:48 Automatic index numbers
Previous Message Brook Milligan 2000-05-17 21:01:35 Re: question on update/delete rules on views