In the following table, the description provides the SQL data type. If you are writing your script in Java or .NET, you should
use the appropriate corresponding data type. See SQL-Java data types and SQL-.NET data types.
In SQL scripts, you can specify event parameters by name or with a question mark. Using question marks has been deprecated
and it is recommended that you use named parameters. You cannot mix names and question marks within a script. If you use question
marks, the parameters must be in the order shown below and are optional only if no subsequent parameters are specified (for
example, you must use parameter 1 if you want to use parameter 2). If you use named parameters, you can specify any subset
of the parameters in any order.
Parameter name for SQL scripts
Order (deprecated for SQL)
VARCHAR(128). The MobiLink remote ID. You can only reference the remote ID if you are using named parameters.
VARCHAR(128). The MobiLink user name.
VARCHAR(128). The MobiLink remote ID, if the remote ID is new in the consolidated database. If the remote ID is not new, the
value is null.
VARCHAR(128). The MobiLink user name, if the user name is new in the consolidated database. If the user name is not new, the
value is null.
The MobiLink server executes this event after receiving everything from the MobiLink client that is required to begin synchronization.
The begin_synchronization script is useful for maintaining statistics. This is because the end_synchronization script is invoked
even if there is an error or conflict, so while the upload transaction is rolled back, things like statistics are maintained.
The following call to a MobiLink system procedure registers a Java method called beginSynchronizationConnection as the script
for the begin_synchronization connection event when synchronizing the script version ver1.