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.

None.

This event occurs immediately before applying the changes that result from rows deleted from the named remote table.

You can have one begin_upload_deletes script for each table in the remote database. The script is only invoked when the table is actually synchronized.

• Script parameters
• Adding and deleting scripts
• end_upload_deletes table event
• Remote IDs and MobiLink user names in scripts

The begin_upload_deletes table event is used to perform whatever steps you need performed after uploading inserts and updates for a particular table, but before deletes are uploaded for that table. The following SQL script creates a temporary table for storing deletes temporarily during upload. This syntax is for a SQL Anywhere consolidated database.

CALL ml_add_table_script(
 'ver1',
 'sales_order',
 'begin_upload_deletes',
 'CREATE TABLE #sales_order_deletes (
    id          integer NOT NULL default autoincrement,
    cust_id     integer NOT NULL,
    order_date  date NOT NULL,
    fin_code_id char(2) NULL,
    region      char(7) NULL,
    sales_rep   integer NOT NULL,
    PRIMARY KEY (id) )' )

The following call to a MobiLink system procedure registers a Java method called beginUploadDeletes as the script for the begin_upload_deletes table event when synchronizing the script version ver1.

CALL ml_add_java_table_script( 
  'ver1', 
  'table1',
  'begin_upload_deletes',
  'ExamplePackage.ExampleClass.beginUploadDeletes' )

The following is the sample Java method beginUploadDeletes. It prints a message to the MobiLink message log. (Note that printing a message to the MobiLink message log might be useful at development time but would slow down a production server.)

package ExamplePackage;
public class ExampleClass {
    String _curUser = null;
public String beginUploadDeletes( 
  String user,
  String table )
  throws java.sql.SQLException {  
  java.lang.System.out.println( 
  "Starting upload deletes for table: " + table );
  return ( null );
}}

The following call to a MobiLink system procedure registers a .NET method called BeginUploadDeletes as the script for the begin_upload_deletes table event when synchronizing the script version ver1 and the table table1.

CALL ml_add_dnet_table_script( 
  'ver1', 
  'table1',
  'begin_upload_deletes',
  'TestScripts.Test.BeginUploadDeletes'
)

The following is the sample .NET method BeginUploadDeletes. It prints a message to the MobiLink message log. (Note that printing a message to the MobiLink message log might be useful at development time but would slow down a production server.)

namespace TestScripts {
public class Test {
  string _curUser = null;   
public string BeginUploadDeletes( 
  string user,
  string table ) {  
  System.Console.WriteLine( 
   "Starting upload deletes for table: " + table );
  return ( null );
}}}