MobiLink Synchronization User's Guide
Adaptive Server Anywhere Clients
The Adaptive Server Anywhere synchronization client, dbmlsync, provides a set of event hooks that you can use to customize the synchronization process. When a hook is implemented, it is called at a specific time during synchronization. You implement an event hook by creating a stored procedure with a specific name. Most event-hook stored procedures are executed on the same connection as the synchronization itself.
You can use event hooks to delay synchronization until a specific condition is met, such as the total number of changes made reaches a set number, a particular change is made, or some data-independent condition.
In addition, you can use event hooks to synchronize subsets of data that cannot be easily defined in a publication. For example, you can synchronize data in a temporary table by writing one event hook procedure to copy data from the temporary table to a permanent table prior to the synchronization and another to copy the data back afterwards.
For more information about specific event-hook procedures, see Client event-hook procedures.
| Caution The integrity of the synchronization process relies on a sequence of built-in transactions. Thus, you must not perform an implicit or explicit commit or rollback within your event-hook procedures. |
Synchronization event hook sequence
Using event-hook procedures