Processes statements in preparation for the synchronization process.
In the following table, the description provides the SQL data type. If you are writing your script in Java or .NET, 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 are going 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 | Description | Order (deprecated for SQL) |
---|---|---|
s.remote_id | VARCHAR(128). The MobiLink remote ID. You can only reference the remote ID if you are using named parameters. | Not applicable |
s.username |
VARCHAR(128). The MobiLink user name. |
1 |
s.new_remote_id | 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. | |
s.new_username | 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. | |
s.script_version | VARCHAR(128). Optional IN parameter to specify that the MobiLink server passes the script version string used for the current synchronization to this parameter. Question marks cannot be used to specify this parameter. | Not applicable |
None.
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.
You may want to store the username value in a temporary table or variable if you are going to reference that value many times in subsequent scripts.
CALL ml_add_connection_script ( 'version1', 'begin_synchronization', 'set @EmployeeID = {ml s.username}' ); |
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.
CALL ml_add_java_connection_script( 'ver1', 'begin_synchronization', 'ExamplePackage.ExampleClass.beginSynchronizationConnection' ) |
The following is the sample Java method beginSynchronizationConnection. It saves the name of the synchronizing user for later use.
package ExamplePackage; public class ExampleClass { String _curUser = null; public void beginSynchronizationConnection( String user ) { _curUser = user; } |
The following call to a MobiLink system procedure registers a .NET method called BeginSync as the script for the begin_synchronization connection event when synchronizing the script version ver1.
CALL ml_add_dnet_connection_script( 'ver1', 'begin_synchronization', 'TestScripts.Test.BeginSync' ) |
The following is the sample .NET method BeginSync. It saves the name of the synchronizing user for later use.
namespace TestScripts { public class Test { string _curUser = null; public void BeginSync( string user ) { _curUser = user; }}} |
![]() |
Discuter à propos de cette page dans DocCommentXchange.
|
Copyright © 2013, SAP AG ou société affiliée SAP - SAP Sybase SQL Anywhere 16.0 |