Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 17 » MobiLink - Server Administration » MobiLink events » Synchronization events » Overview of MobiLink events

MobiLink event model notes

Keep the following points in mind:

  • Usually, if you have not defined a script for a given event, the default action is to do nothing.

  • The begin_connection and end_connection events are connection-level events. They are independent of any single synchronization and have no parameters.

  • Some events are invoked once per synchronization for each table being synchronized. Scripts associated with these events are called table-level scripts.

    While each table can have its own table scripts, you can also write table-level scripts that are shared by several tables.

  • Some events, such as begin_synchronization, occur at both the connection level and the table level. You can supply both connection and table scripts for these events.

  • The COMMIT statements illustrate how the synchronization process is broken up into distinct transactions.

Caution There should be no implicit or explicit commit or rollback in your SQL synchronization scripts or the procedures or triggers that are called from your SQL synchronization scripts. COMMIT or ROLLBACK statements within SQL scripts alter the transactional nature of the synchronization steps. If you use them, MobiLink cannot guarantee the integrity of your data in the event of a failure.