Losing data? As a developer, I have always taken the approach of delete nothing. Delete is not an SQL command I use. Instead, use an additional column such as 'active'. Then, when the s/&t hits the fan, it's probably a selection issue or some such. Easy to analyse and fix.

And of course, not deleting anything also means I can respond to complaints of the "I didn't do it" sort by looking at the active column of the row and the last user who updated the row, and replying "oh yes you did"

Is it panto season yet?