Forced conflict resolution is a special technique that forces every uploaded row to be treated as if it were a conflict.
The MobiLink server uses forced conflict resolution when the upload_insert, upload_update, and upload_delete script are all undefined. In this mode of operation, the MobiLink server attempts to insert all uploaded rows from that table using the statements defined by the upload_old_row_insert and upload_new_row_insert scripts. In essence, all uploaded rows are then treated as conflicts. You can write stored procedures or scripts to process the uploaded values in any way you want.
Normal conflict-resolution occurs when an upload_fetch or upload_fetch_column_conflict script is defined. Without any of the upload_insert, upload_update, or upload_delete scripts, the normal conflict-resolution procedure is bypassed. This technique has two principal uses.
Arbitrary conflict detection and resolution The automatic mechanism only detects errors when updating a row, and only then when the old values do not match the present values in the consolidated database.
You can capture the raw uploaded data using the upload_old_row_insert and upload_new_row_insert scripts, then process the rows as you see fit.
Performance When the upload_insert, upload_update, and upload_delete are not defined, the MobiLink server is relieved of its normal conflict-detection tasks, which involve querying the consolidated database one row at a time. Instead, it needs only to insert the raw uploaded information using the statements defined by the upload_old_row_insert and upload_new_row_insert scripts. Performance is improved because the MobiLink server is not fetching rows across the network.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|