Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
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:
Row-based conflict detection A conflict is detected if the row has been updated by both the remote and consolidated databases since the last synchronization.
This option defines an upload_fetch script and upload_update script. See Conflict detection with upload_fetch or upload_fetch_column_conflict scripts.
Column-based conflict detection A conflict is detected if the same column has been updated for the row in both the remote and consolidated databases.
This option defines an upload_fetch_column_conflict script. See Conflict detection with upload_fetch or upload_fetch_column_conflict scripts.
If a table has BLOBs and you choose column-based conflict detection, row-based conflict detection is used.
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.
Modifying conflict detection and resolution
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|