Specifications

CHAPTER 4 Working with Data Pipelines
Users Guide 133
When you stop
execution
When you click Cancel or a Query Governor limit is reached, if the Commit
value is a number, every row that was piped is committed. If the Commit value
is
All or None, every row that was piped is rolled back.
For example, if you click the Cancel button when the 24th row is piped and the
Commit value is 20, then:
1 20 rows are piped and committed.
2 3 rows are piped and committed.
3 Piping stops.
If the Commit value is
All or None, 23 rows are rolled back.
When InfoMaker stops
execution
InfoMaker stops execution if the error limit is reached. Table 4-4 shows how
the Commit and Max Errors values affect the number of rows that are piped and
committed.
Table 4-4: Rows committed when InfoMaker stops execution
For example, if an error occurs when the 24th row is piped and the Commit
value is 10 and the Max Errors value is 1, then:
1 10 rows are piped and committed.
2 10 rows are piped and committed.
3 3 rows are piped and committed.
4 Piping stops.
If the Commit value is
All or None, 23 rows are rolled back.
Commit value Max Errors value Result
A number n
No limit or a number
m
Rows are piped and committed n
rows at a time until the Max Errors
value is reached.
All or None No limit Every row that pipes without error is
committed.
All or None A number n If the number of errors is less than n,
all rows are committed.
If the number of errors is equal to n,
every row that was piped is rolled
back. No changes are made.