Specifications

Modifying the data pipeline definition
132 InfoMaker
When using Update
For the Update - Update/Insert Rows option, the destination table must already
exist. You can:
• Select an existing table from the Table drop-down list.
• Modify the Commit and Max Errors values.
• Change the Key columns in the destination table’s primary key or unique
index, depending on what the DBMS supports. Key columns must be
selected; the key determines the
UPDATE statement’s WHERE clause.
• Change the initial value for a column.
Bind variables and the Update option
If the destination database supports bind variables, the Update option takes
advantage of them to optimize pipeline execution.
When execution stops
Execution of a pipeline can stop for any of these reasons:
• You click the Cancel button
During the execution of a pipeline, the Execute button in the PainterBar
changes to a Cancel button.
• The error limit is reached
• The Query Governor’s row or elapsed-time limit is reached
If there are rows that cannot be piped to the destination table for some reason,
those error rows display once execution stops. You can correct error rows or
return to the workspace to change the pipeline definition and then execute it
again. For information, see “Correcting pipeline errors” on page 137.
Whether rows are committed
When rows are piped to the destination table, they are first inserted and then
either committed or rolled back. Whether rows are committed depends on:
• What the Commit and Max Errors values are
• When errors occur during execution
• Whether you click the Cancel button or InfoMaker stops execution