Greenplum Delete

Use this activity to delete a record from the Greenplum database.

Configuration

The Configuration tab has the following fields:

Field Description
Connection Name of the PostgreSQL database connection from which information is retrieved. You can select the connection from the drop-down list.

Input Settings

The Input Settings tab has the following fields:

Field Description
Delete A SQL query used to delete the record from the table. You can construct prepared SQL queries by using substitution variables (or parameters) of the form ?<fieldname> in the delete query statement.
Each substitution variable identifies an input parameter. The mapped value of the input parameter is added in the substitution variable at run time. You can reuse the substitution variable for the same input parameter elsewhere in the query. Information about the type of input parameters used in the WHERE clause is fetched from the database by using the connection that you have selected for the delete query. Similarly, input fields on the Input tab of the activity are also automatically generated.
Note: Include a semicolon (;) at the end of the query to indicate the end of the query. A missing semicolon at the end of the query results in a syntax error.
The following example represents a typical delete query:
Delete from advisor where i_id=?i_id;
The delete query in this example does not have an output field. An input field is generated for i_id (VARCHAR). Also the mapped value for the field name is substituted in the ?i_id substitution variable.
Fields The grid is provided for information purpose only.

Input

This tab displays the input schema of the activity in a tree structure format. The information in the schema varies based on the delete query provided. The fields that were selected on the Input Settings tab are available in the schema. You can either hard code the values or map them to a field from the output of a preceding activity in the flow by using the Mapper.

Output

The Output tab displays the output schema of the activity in a tree structure format. The output is read-only. The information in the schema varies based on the fields selected on the Configuration tab. The properties that are displayed in the schema correspond to the output of this activity and can be used as input by subsequent activities in the flow.