>Allow me to fall into Cassandra syndrome (without any gender over- or undertones) for a moment:
>For a backend NOT using delete/insert for update I'd guess the same as Kevin.
>But STILL undefined area between ears suggests it is a bad idea.

Generally, I agree with you.
Again, I realize some environments have so much invested in the approach they've been using for years, that to change it would require a huge undertaking.

As a general statement, nearly every environment I've been in has REQUIRED that Insert/update statements can ONLY be done in the database....period. Even though I generally agree with that anyway, I was surprised to learn even 15 years ago the # of places that had that as a pure auditing requirement.

Not a value judgement - but generally, I agree with you.