Writing download_cursor scripts

You write download_cursor scripts to download rows from the consolidated database to your remote database. Similarly, you write download_delete_cursor scripts to download rows to delete from the remote database. You must write both of these scripts for each table in the remote database for which you want to download changes. You can use other scripts to customize the download process, but no others are necessary.

Each download_cursor script that you want to download rows must contain a SELECT statement or a call to a procedure that contains a SELECT statement.
If you do not want download rows, define the script as --{ml_ignore}. Alternatively, you can use the ml_add_missing_dnld_scripts system procedure to define missing download scripts as ignored. See ml_add_missing_dnld_scripts system procedure.
The download_cursor script must select all columns that correspond to the columns in the corresponding table in the remote database. The columns in the consolidated database can have different names than the corresponding columns in the remote database, but they must be of compatible types.

Example

The following script could serve as a download_cursor script for a remote table that holds employee information. This script downloads information about all the employees.

SELECT emp_id, emp_fname, emp_lname
FROM employee;

The MobiLink server passes specific parameters to some scripts. The MobiLink server substitutes the value of the parameter before executing the statement against the consolidated database. The use of question marks has been deprecated in SQL scripts. The following script shows how you can use named parameters:

CALL ml_add_table_script( 
   'Lab',
   'ULOrder',
   'download_cursor',
   'SELECT o.order_id, o.cust_id, o.prod_id, o.emp_id, o.disc, o.quant, o.notes, o.status
         FROM ULOrder o
         WHERE o.last_modified >= {ml s.last_table_download}
               AND o.emp_name = {ml s.username}' )

Notes

All cursor scripts must select the columns in the same order as the columns are defined in the remote database. Where column names or table structure is different in the consolidated database, columns should be selected in the correct order for the remote database, or equivalently, the reference database. Columns are assigned to columns in the remote database based on their order in the SELECT statement.
Row values can be selected from a single table or from a join of multiple tables.
The remote table need not have the same name as the table in the consolidated database. The script itself need not include the name of the remote table. The name of the remote table is identified by an entry in the ml_table MobiLink system table. Use Sybase Central to view the remote tables listed together with their scripts.

Writing download_cursor scripts

Example

Notes

See also