The Conflict Handling tab lets you define what happens when a row is modified both in the consolidated database and on a remote database.
Conflict Detection This option determines when a conflict is detected. The conflict resolution mechanism is only activated when a conflict is detected.
Choose one of the following options from the dropdown list.
Row-based A conflict is detected if the row has been updated on both the remote and the consolidated database since the last synchronization.
Column-based A conflict is detected only if the same column has been updated for the row in both the remote and consolidated databases. Otherwise, only the uploaded column updates are applied. If a table has BLOB columns, row-based conflict detection is used instead.
Conflict Resolution Choose one of the following options for conflict resolution from the dropdown list:
Consolidated First in wins. Uploaded updates are rejected if they conflict.
Remote Last in wins. Uploaded updates are always applied.
Timestamp The newer change wins, using a TIMESTAMP column that you maintain. This TIMESTAMP column records the last time that the row was changed. It should exist in both the remote and consolidated tables and be included in the synchronization. To work, your remote and consolidated databases must use the same time zone (preferably UTC) and their clocks must be synchronized.
Timestamp column Enter the TIMESTAMP column here.
Custom Write your own resolve_conflict scripts instead of having them generated automatically. You can do this on the Events tab.
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0 |