ml_passthrough_script

Stores the names and contents for each passthrough script.

Column

Description

script_id

INTEGER. A unique integer that identifies the passthrough script name. This value is used internally.

script_name

VARCHAR(128). The unique passthrough script name.

flags

VARCHAR(256). This value tells clients how to run the script. This value can be null or contain a combination of the following keywords in a semicolon-delimited list:

  • manual   Indicates that the script may only be run in manual execution mode. By default, all scripts can be run in either automatic or manual execution modes.

  • exclusive   Indicates that the script may only be automatically executed at the end of a synchronization where exclusive locks were obtained on all tables being synchronized. This option is ignored if the affected_ publications value lists no publications. This option is only meaningful to SQL Anywhere remotes.

  • schema_diff   Indicates that the script should be run in schema-diffing mode. In this mode, the database schema is altered to match the schema described in the script. For example, a create statement for an existing table is treated as an alter statement. This flag only applies to scripts run on UltraLite remotes.

For example: 

'manual;exclusive;schema_diff'

affected_pubs

TEXT. A list of publications that must be synchronized before the script is run. An empty or null publication list indicates that no synchronization is required. This value is only meaningful with SQL Anywhere clients.

script

TEXT. The contents of the passthrough script.

description

VARCHAR(2000). A comment or description of the script.
Remarks

You can use the ml_add_passthrough_script system procedure and the ml_delete_passthrough_script system procedure to add and delete entries in this table.

It is recommended that you do not directly update the ml_passthrough_script table without using the ml_add_passthrough_script and ml_delete_passthrough_script system procedures. Clients do not receive newly updated scripts if they have already downloaded the original passthrough scripts. Discrepancies between the various scripts on multiple clients makes managing script execution difficult or impossible.

For DB2 mainframe consolidated database types, this table is called ml_pt_script. See IBM DB2 mainframe system table name conversions.

Constraints

PRIMARY KEY( script_id )

See also
Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0