Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
When a MobiLink client sends an updated row to the MobiLink server, it includes not only the new updated values (the post-image), but also a copy of the old row values (the pre-image) obtained either in the last download or from the row values existing before the first upload of this row. When the pre-image does not match the current values in the consolidated database, a conflict is detected.
The MobiLink server detects conflicts only if an upload_fetch or upload_fetch_column_conflict script is applied. When you use upload_fetch, conflicting updates are flagged as a conflict. When you use upload_fetch_column_conflict, only conflicts on updates to the same column are flagged.
You can also set up arbitrary conflict detection and resolution using a stored procedure for upload_update. Conflict detection and resolution is completely controlled by the script so MobiLink does not trigger a conflict.
Conflict detection with upload_fetch or upload_fetch_column_conflict scripts
Conflict detection with upload_update scripts
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|