Dependency of modifications on pipeline operation

The modifications you can make in the workspace depend on the pipeline operation you have chosen.

When using Create or Replace

When you select the Create - Add Table option (the default) or the Replace - Drop/Add Table option, you can:

Change the destination table definition.

Follow the rules of the destination DBMS.
Specify or clear a key name and/or key columns.

Specify key columns by selecting one or more check boxes to define a unique identifier for rows. Neither a key name nor key columns are required.
Allow or disallow NULLs for a column.

If NULL is allowed, no initial value is allowed. If NULL is not allowed, an initial value is required. The words spaces (a string filled with spaces) and today (today’s date) are initial value keywords.
Modify the Commit and Max Errors values.
Specify an initial value and a default value.

If you have specified key columns and a key name and if the destination DBMS supports primary keys, the Data Pipeline painter creates a primary key for the destination table. If the destination DBMS does not support primary keys, a unique index is created.

For Oracle databases InfoMaker generates a unique index for Oracle databases.

If you try to use the Create option, but a table with the specified name already exists in the destination database, InfoMaker tells you, and you must select another option or change the table name.

When you use the Replace option, InfoMaker warns you that you are deleting a table, and you can choose another option if needed.

When using Refresh and Append

For the Refresh - Delete/Insert Rows or Append - Insert Rows options, 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 initial value for a column.

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.