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

SAP Sybase SQL Anywhere 16.0 » MobiLink - Getting Started » MobiLink technology » MobiLink plug-in for Sybase Central » Synchronization models » Synchronization model tasks


Conflict detection and resolution

When a row is updated on both the remote and consolidated databases, a conflict occurs the next time that the databases are synchronized.

You have the following options for detecting conflicts:

You have the following options for resolving conflicts:

  • Consolidated   First in wins: uploaded updates that conflict are discarded.

  • Remote   Last in wins: uploaded updates are always applied.

  • Timestamp   The newest update wins. To use this option, you must create and maintain a TIMESTAMP column for the table. This TIMESTAMP column should record the last time that a row was changed. The column should exist on both the consolidated and remote databases and not be the same column used for timestamp-based downloads. To work, your remote and consolidated databases must use the same time zone (preferably UTC) and their clocks must be synchronized.

  • Custom   You write your own resolve_conflict scripts. You do this on the Events tab. See Conflict resolution with resolve_conflict scripts.

 See also

Modifying conflict detection and resolution