MobiLink Synchronization Reference
Stored Procedures
Client event-hook procedures
Use this stored procedure to add custom actions immediately after the transaction log is scanned for upload.
| Name | Values | Description |
|---|---|---|
| ending log offset (in) | number | The log offset value where scanning ended. |
| starting log offset_n (in) | number | The log offset value where scanning began. |
| log scan retry (in) | True|False | If this is the first time the transaction log has been scanned for this synchronization, the value is false; otherwise it is true. The log is scanned twice when the MobiLink synchronization server and dbmlsync have different information about where the scanning should begin. |
| publication_n (in) | publication name | The publications being synchronized, where n is an integer. There is one publication_n entry for each publication being uploaded. |
| MobiLink user (in) | MobiLink user name | The MobiLink user for which you are synchronizing. |
| script version (in) | script version name | The MobiLink script version to be used for the synchronization. |
If a procedure of this name exists, it is called immediately after dbmlsync has scanned the transaction log to assemble the upload stream.
Actions of this procedure are committed immediately after execution.
Synchronization event hook sequence