Re: delete cascade
From: paul c <toledobythesea_at_oohay.ac>
Date: Sun, 22 Apr 2007 05:14:49 GMT
Message-ID: <dbCWh.114575$DE1.5577_at_pd7urf2no>
>
> That is intriguing about RVA's. Do you have in mind entwining the
> notion of an invoice transaction with a reference constraint by not
> assigning the rva until it is known (by some program) that all items
> have been inserted (into some table or other)?
Date: Sun, 22 Apr 2007 05:14:49 GMT
Message-ID: <dbCWh.114575$DE1.5577_at_pd7urf2no>
paul c wrote:
> Bob Badour wrote:
>
>> ... >> More and more, I am liking "on delete" or "on update" less and less. I >> suggest the appropriate place to handle the issue is in the view >> specification. If one wants "on delete cascase", one can present a >> view with the invoice items as an RVA. >> ...
>
> That is intriguing about RVA's. Do you have in mind entwining the
> notion of an invoice transaction with a reference constraint by not
> assigning the rva until it is known (by some program) that all items
> have been inserted (into some table or other)?
Eg., the rva has an attribute that references the invoice# in the same
relation that has the rva as an attribute.
p