Re: delete cascade
From: Bob Badour <bbadour_at_pei.sympatico.ca>
Date: Mon, 16 Apr 2007 16:51:26 GMT
Message-ID: <iQNUh.25100$PV3.253032_at_ursa-nb00s0.nbnet.nb.ca>
>>paul c wrote:
>>
>>
>>>>Because some times it means: "If a line item exists, the invoice must
>>>>also exist."
>>
>>>Please forgive my thickness, but doesn't "line item doesn't exist
>>>unless..." (ie., "only if") "...the invoice exists" mean the same?
>>
>>No. One states that deleting the invoice automatically deletes any items
>>that exist. The other states that one may not delete an invoice when any
>>items exist.
Date: Mon, 16 Apr 2007 16:51:26 GMT
Message-ID: <iQNUh.25100$PV3.253032_at_ursa-nb00s0.nbnet.nb.ca>
Marshall wrote:
> On Apr 16, 5:56 am, Bob Badour <bbad..._at_pei.sympatico.ca> wrote: >
>>paul c wrote:
>>
>>
>>>>Because some times it means: "If a line item exists, the invoice must
>>>>also exist."
>>
>>>Please forgive my thickness, but doesn't "line item doesn't exist
>>>unless..." (ie., "only if") "...the invoice exists" mean the same?
>>
>>No. One states that deleting the invoice automatically deletes any items
>>that exist. The other states that one may not delete an invoice when any
>>items exist.
> > Is this anything other than a convenience? (Not that I don't value > convenience.)
Assuming one can have a triggered procedure cascade deletes, it is a short-hand for doing so. However, I prefer declarations to procedures, which makes me consider it something more than mere convenience. Received on Mon Apr 16 2007 - 18:51:26 CEST