When you specify TableOrder, determines whether dbmlsync should check that no table is uploaded before another table on which it has a foreign key.

Syntax

tor={ OFF | ON }; ...

Remarks

In most applications, tables on the remote and consolidated databases have the same foreign key relationships. In these cases, you should leave TableOrderChecking at its default value of ON, and dbmlsync ensures that no table is uploaded before another table on which it has a foreign key. This ensures referential integrity.

This option is useful when the consolidated and remote databases have different foreign key relationships. Use it with the TableOrder extended option to specify an order of tables that does not follow the rule that no table is uploaded before one on which it has a foreign key.

This option is only useful when the TableOrder extended option is specified.

The default is ON.

This option has a short form and long form: you can use toc or TableOrderChecking.

You can also store extended options in the database. For more information about dbmlsync extended options, see Introduction to dbmlsync extended options.

See also

• TableOrder (tor) extended option
• How the upload is processed
• Referential integrity and synchronization

Example

The following dbmlsync command line illustrates how you can set this option when you start dbmlsync:

dbmlsync -e "toc=OFF"

The following SQL statement illustrates how you can store this option in the database:

CREATE SYNCHRONIZATION SUBSCRIPTION
   TO sales_publication
   FOR ml_user1
   OPTION toc='Off';