I’ve just discovered that the result flags returned by JDBC Update and BatchUpdate services can be incorrect if database triggers are defined on the underlying table.
For instance, if I call an Update service for a record that doesn’t exist, the result flag should be 0. However, the service is returning 1, and this appears to be due to SQL Server database triggers. It’s quite bizarre, as I can’t understand why SQL Server is firing triggers in the first place, given there’s no record to update (but it definitely is firing them!)
Any suggestions (apart from the rather tempting “remove the DB triggers”)?