Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.1 » MobiLink - Server Administration » MobiLink server technology » Synchronization techniques » Conflict handling » Conflict detection


Conflict detection with upload_new_row_insert or upload_old_row_insert scripts

If you define either an upload_new_row_insert or upload_old_row_insert script for a table without defining the upload_fetch and upload_fetch_column_conflict scripts, the MobiLink server uses the number of rows affected by the upload updates to determine if a conflict has occurred.

If the MobiLink server is attempting to upload multiple rows during a conflict and the number of affected rows is less than the number of rows applied to the consolidated database, then the server uploads each row individually to re-apply the upload updates. However, if the MobiLink server is attempting to upload a single row and the number of affected rows is zero after the upload update, then the server treats the update as a conflict update. For more information about uploading multiple rows, see -s mlsrv12 option.


The number of affected rows count is not always reliable. The MobiLink server could trigger an incorrect conflict update and call the conflict resolution scripts mistakenly if the affected row count is not correct.

 See also