MobiLink Synchronization Reference
  Synchronization Events

begin_publication connection event

Function 

Provides useful information about the publication(s) being synchronized. This script may also be used to manage generation numbers for file-based downloads.

Parameters 

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.

Default action 

The default generation number is 1. If no script is defined for this event, the generation number sent to the remote will always be 1.

Description 

This event lets you design synchronization logic based on the publications currently being synchronized. This event is invoked in the same transaction as the begin_synchronization event, and is invoked after the begin_synchronization event. It is invoked once per publication being synchronized.

One potential use for this event is to affect what is downloaded based on the publication used. For example, consider a table that is part of both a priority publication (PriorityPub) and a publication for all tables (AllTablesPub). A script for the begin_publication event could store the publication names in a Java class or a SQL variable or package. Download scripts could then behave differently based on whether the publication being synchronized is PriorityPub or AllTablesPub.

Generation number 

The generation_number parameter is specifically for file-based downloads. The output value of the generation number is passed from the begin_synchronization script to the end_synchronization script. The meaning of the generation_number depends on whether the current synchronization is being used to create a download file, or whether the current synchronization has an upload.

The output value of the generation number is passed from the begin_publication script to the end_publication script. The meaning of the generation_number depends on whether the current synchronization is being used to create a download file, or whether the current synchronization has an upload.

In file-based downloads, generation numbers are used to force an upload before the download. The number is stored in the download file. During a synchronization that has an upload, one generation number is output for every subscription to a publication. They are sent to the remote database in the upload acknowledgement, and stored in SYSSYNC.generation_number.

See also 

end_publication connection event

File-Based Downloads

SQL example 

You may want to record the information for each publication being synchronized:

call ml_add_connection_script(
'version1',
'begin_publication',
'{call RecordPubSync( ?, ?, ?, ?, ? )}' );

Java example 

The following stored procedure call registers a Java method called beginPublication as the script for the begin_publication connection event when synchronizing the script version ver1. This syntax is for Adaptive Server Anywhere consolidated databases.

call ml_add_java_connection_script( 'ver1',
   'begin_publication',
   'ExamplePackage.ExampleClass.beginPublication' )

Following is the sample Java method beginPublication. It saves the name of each publication for later use.

public String beginPublication(
    ianywhere.ml.script.InOutInteger generation_number,
    String user,
    String pub_name,
    Timestamp last_upload,
    Timestamp last_download )
{  _publicationNames[ _numPublications++ ] = pub_name;
   return( null ); }

.NET example 

The following stored procedure call registers a .NET method called BeginPub as the script for the begin_publication connection event when synchronizing the script version ver1. This syntax is for Adaptive Server Anywhere consolidated databases.

call ml_add_dnet_connection_script( 'ver1',
  'begin_publication',
  'TestScripts.Test.BeginPub'
)

Following is the C# signature for BeginPub.

public void BeginPub(
    ref int generation_number,
    string user,
    string pub_name,
    DateTime last_upload,
    DateTime last_download )
{
    _publicationNames[ _numPublications++ ] = pub_name;
}