Data Transformation Engine Database Interface Designer Reference Guide

Chapter 9 - Database Triggers Specifying a Combination of Different Event Classes

Database Interface Designer Reference Guide

140

Defining Events

Use the Trigger Specification dialog box to define a trigger specification for an

individual query that will be stored with the query in the .mdq file. As you add and

remove the table names, the lists on the right display the tables for which an

Insert into, Delete from, or Update of event comprises the condition(s) that

must be met for the trigger specification. Additionally, you can specify whether

row-based triggering will be used. The different classes of events that you can

specify are:

♦ Insert into

The insertion of rows into the specified table serves as an input event trigger to

the map that uses this query as a data source.

♦ Delete from

The deletion of rows from the specified table serves as an input event trigger to

the map that uses this query as a data source.

Note This functionality cannot be used with row-based triggering. As soon as

you move a table to the right, the Row-based triggering check box is

disabled.

♦ Update of

The update of rows in the specified table will serve as an input event trigger to

the map that uses this query as a data source.

Specifying a Combination of Different Event Classes

If you define your trigger specification using a combination of event classes

(Insert into, Delete from or Update of), there is an implicit OR between the

different event classes.

For example, if you defined events in all three event classes, the implied condition

to be met for the trigger specification would be:

Insert into TableA

Delete from TableB

Update of TableC

When all events have occurred within only one of the specified event classes, the

condition(s) has/have been met for the trigger specification and the map is run.