Re: Cascading Deletes
Date: Sat, 10 Feb 2001 11:24:02 +0100
Message-ID: <9634sg$e8bh$1_at_as121.tel.hr>
In my own experience, I'll have to agree with you. I've seen cases when
clients deleted lots of records they didn't intend to, though they were
warned about this several times. Users will usually forget, and don't count
on cascading (average user has never heard of it). Restrictions prevent
developer messing things,too. I had to do lots of ad hoc
queries/updates/deletes on production db, on short notice. Saved me few
times. Though I think that sometimes it is very usefull, and it should be
decided depending on individual case, rather than as a general rule. Don't
think there is a general answer like yes or no to your question.
HTH,
Goran
Todd Taylor wrote in message ...
>My company is having an internal discussion about whether or not the
>practice of using cascading deletes in a database is good or bad, and I
>wanted to get some outside opinions on the subject.
>
>I am arguing that they should never be used.
>
>
...
>Thank you,
>
>Todd Taylor
>ProActive Technology, LLC
>
>
>
>
>
Received on Sat Feb 10 2001 - 11:24:02 CET