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, but you cannot mix names and question marks within a script. 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.

The download_statistics event allows you to gather, for any user, statistics on downloads. The download_statistics connection script is called just before the commit at the end of the download transaction.

• Script parameters
• Adding and deleting scripts
• download_statistics table event
• upload_statistics connection event
• upload_statistics table event
• synchronization_statistics connection event
• synchronization_statistics table event
• time_statistics connection event
• time_statistics table event
• MobiLink Monitor
• Remote IDs and MobiLink user names in scripts

The following example inserts synchronization statistics into a table called download_audit.

CALL ml_add_connection_script(
 'ver1', 
 'download_statistics', 
 'INSERT INTO download_audit(
   user_name, 
   warnings, 
   errors, 
   fetched_rows,
   deleted_rows,  
   filtered_rows, 
   bytes )
  VALUES (
   {ml s.username}, 
   {ml s.warnings}, 
   {ml s.errors}, 
   {ml s.fetched_rows}, 
   {ml s.deleted_rows}, 
   {ml s.filtered_rows}, 
   {ml s.bytes})')

Once vital statistics are inserted into the audit table, you may use these statistics to monitor your synchronizations and make optimizations where applicable.

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

CALL ml_add_java_connection_script(
  'ver1',
  'download_statistics',
  'ExamplePackage.ExampleClass.downloadStatisticsConnection' )

The following is the sample Java method downloadStatisticsConnection. It prints the number of fetched rows to the MobiLink message log. (Note that printing the number of fetched rows 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 downloadStatisticsConnection(
  String user,
  int warnings,
  int errors,
  int fetchedRows,
  int deletedRows,
  int filteredRows,
  int bytes ) {
  java.lang.System.out.println( 
   "download connection stats fetchedRows: " 
   + fetchedRows );
  return ( null );
}}

The following call to a MobiLink system procedure registers a .NET method called DownloadStats as the script for the download_statistics connection event when synchronizing the script version ver1.

CALL ml_add_dnet_connection_script(
  'ver1',
  'download_statistics',
  'TestScripts.Test.DownloadStats'
)

The following is the sample .NET method DownloadStats. It prints the number of fetched rows to the MobiLink message log. (Note that printing the number of fetched rows 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 DownloadStats(
  string user,
  int warnings,
  int errors,
  int deletedRows,
  int fetchedRows,
  int downloadRows,
  int filteredRows,
  int bytes ) {  
  System.Console.WriteLine( 
   "download connection stats fetchedRows: " 
   + fetchedRows );
  return ( null );
}}}