marlon.seton (3/21/2013)
Lokesh Vij (3/20/2013)
db4breakfast (3/20/2013)
I never use cascade delete on a production db. It seem to be safer by allowing users mark order as "error" instead.+1
same here. i feel it is dangerous to use on delete cascade in production...as a mistake in deleting a parent records will trigger deletes from all the child records :w00t:
We use triggers to delete the child records when a parent record is deleted. Is that generally considered a bad thing to do?
I don't want to be provocative or offensive here, but I really don't know how to avoid it: writing a trigger to do what "with cascade" would do is pure illogical insanity. If my saying that helps you change your mind, I'll have done you a favour, so I guess being blunt is excusable.
Tom