Some tables are self-referencing. For example, an employee table may contain a column that lists employees and a column that lists the manager of each employee, and there may be a hierarchy of managers managing managers. These tables can pose a challenge to synchronization because the MobiLink default behavior is to coalesce all data updates on the remote database, which is efficient but which loses the order of transactions.
There are two techniques for handling this situation:
If you are using a SQL Anywhere remote database, you can use the dbmlsync -tu option to specify that each transaction on the remote should be sent as a separate transaction. See -tu dbmlsync option.
Add a mapping table, mapping employees to managers, so the order of transactions in the formerly self-referencing table no longer matters.
Discuss this page in DocCommentXchange.
|Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0|