Re: delete cascade
From: paul c <toledobythesea_at_oohay.ac>
Date: Mon, 23 Apr 2007 21:47:16 GMT
Message-ID: <EP9Xh.118822$DE1.53489_at_pd7urf2no>
>
>
> I didn't refer to two selects and a join so I find your comment
> confusing. I was discussing a single delete that deletes both just as an
> "on delete cascade" trigger would delete both.
Date: Mon, 23 Apr 2007 21:47:16 GMT
Message-ID: <EP9Xh.118822$DE1.53489_at_pd7urf2no>
Bob Badour wrote:
> paul c wrote:
...
>>> I mention it because it would fully disclose the data to be deleted, >>> which is the invoice and the associated items. >> >> >> I can see that it would fully enclose, ie., enclose in one relation, >> but not sure how it would disclose any more fully than two selections >> and a join. >> >> Not trying to be picky but I found your view suggestion to be profound >> and want to make sure I understand this one.
>
>
> I didn't refer to two selects and a join so I find your comment
> confusing. I was discussing a single delete that deletes both just as an
> "on delete cascade" trigger would delete both.
I had an example like this in mind:
V = (invoices where invoice# = 99) <AND> (items where invoice# = 99);
DELETE V;