From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | André Næss <andre(dot)nass(at)student(dot)uib(dot)no> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Conditional rule? |
Date: | 2000-07-28 15:13:31 |
Message-ID: | 29738.964797211@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"=?iso-8859-1?B?QW5kcukgTuZzcw==?=" <andre(dot)nass(at)student(dot)uib(dot)no> writes:
> Secondly, I miss one final idea, when a delete is performed on the
> b_news_unpublished table, I would like to set up a rule or procedure that
> sets the time value to null in b_news for each row that is affected by the
> delete. I understand that the OLD and NEW objects are accessible only during
> UPDATE or INSERT operations, so I can't quite see how to do this...
I might be wrong, but I thought the way it works is:
INSERT: "NEW" refers to to-be-inserted row
UPDATE: "OLD" is old row state, "NEW" is planned new row state
DELETE: "OLD" holds row to be deleted
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Henry Lafleur | 2000-07-28 16:18:08 | RE: RE: Re(2): optimize sql |
Previous Message | André Næss | 2000-07-28 11:46:51 | Re: Conditional rule? |