A conflict occurs when a row has been updated on both the remote and consolidated databases since the last synchronization. This page allows you to set the level of conflict detection used.
This page has the following components:
No conflict detection Select this option if you do not want any conflict detection. Uploaded updates are applied without checking for conflicts. This avoids having to fetch current row values from the consolidated database, so the synchronization of updates may be faster.
Row-based conflict detection Select this option to use row-based conflict detection on upload. A conflict is detected if the row has been updated by both the remote and consolidated databases since the last synchronization. See upload_fetch table event and upload_update table event.
Column-based conflict detection Select this option to use 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. See upload_fetch_column_conflict table event.
You can view and modify these options, after the Create Synchronization Wizard finishes, in the Model mode Mappings tab. See Modifying conflict detection and resolution.
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|