The optimistic conflict check is now done for deletions. Because of this, the record is refreshed from server and can be deleted on next attempt.
To accomplish the check, fetchDBRowForUpdate (which fetches the record and also performs the delete) now calls compareDBrow. In previous releases, compareDbRow was called after fetchDBRowForUpdate had completed. While these procedures generally are not intended for direct calls and local overrides, they can have general application-specific customizations which this change might affect. The most important change of behavior to consider is that compareDBRow now is called for deletes.
