Fetches rows from a synchronized table in the consolidated database for the purpose of column-level conflict detection.
Parameter name for SQL scripts |
Order |
---|---|
r.pk-column-1 |
1 |
... | ... |
r.pk-column-N |
N |
r.column-1 |
N + 1 |
... |
... |
r.column-M |
N + M |
None.
The statement-based upload_fetch_column_conflict script fetches columns from a synchronized table for the purposes of conflict detection. It is a companion to the upload_update event.
This script only detects a conflict when two users update the same column. Different users can update the same row, as long as they don't update the same column, without generating a conflict.
For example, using the upload_fetch_column_conflict script, you could avoid detecting a conflict when one of your remote users updated the quant column of the ULOrder table, and another remote user updated the notes column for the same row. You would only detect a conflict if they both updated the quant column.
You can have only one upload_fetch or upload_fetch_column_conflict script for each table in the remote database.
This script may be ignored if none of the following scripts are defined: upload_new_row_insert, upload_old_row_insert, and resolve_conflict.
Discuss this page in DocCommentXchange. Send feedback about this page using email. |
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1 |