Oracle Database Update

Settings

The Settings tab has the following fields:

Field	Description
Oracle Database Connection	Name of the Oracle Database connection from which to retrieve information. You can select the connection from the Oracle Database Connection dropdown list.
Schema	Enter the appropriate schema from the Oracle Database.

Input Settings

The Input Settings tab has the following fields:

Field	Description
Update Statement	An SQL statement used to update a record in the table. You can construct prepared SQL queries by using substitution variables (or parameters) of the form ?<fieldname> in the update query statement. As you begin typing a query, the auto-suggest dropdown menu displays relevant keywords, table names, and column names that you can select from. To choose a column name from the dropdown menu, first type the table name followed by a period (.), which shows the list of available column names for that table. If you are unfamiliar with the tables present in the database schema, press the CTRL + space key in the query editor to obtain auto-suggestion of all the tables and keywords present in the database schema. Each substitution variable identifies an input parameter whose mapped value is substituted in the substitution variable at runtime. You can reuse the substitution variable for the same input parameter elsewhere in the query. The input fields in the Input tab of the activity are populated based on the SQL UPDATE statement. You must include the semicolon (;) at the end of the query. This activity expects an update query to end with a semicolon to indicate the end of the query. A missing semicolon at the end results in the query being unresponsive. For now, only single table update queries are allowed. Example of UPDATE query: update SYSTEM.student set roll_no = ?roll_no where name like ?name; For the above update query, roll_no(NUMBER) and name(VARCHAR) are in the Inputs tab as these fields are used as parameters. Also, the mapped values for the fields name and roll_no are substituted in the substitution variables ?name and ?roll_no at runtime. Call Procedure and Call Functions Syntax: With no parameters Call Procedure_Name( ); Select Function_Name( ); With prepared parameters Call Procedure_Name(?Param1 , ?Param2); Select Function_Name(?Param1, ?Param2);
Manually Configure Metadata	Set the Manually Configure Metadata field to True to fetch table metadata manually. For more information, see Using Manually Configure Metadata Option. Note: Schema retrieval may fail if nonstandard SQL is used.
Table Schema	Displays the metadata of the SQL update statement. You can modify the column metadata if Manually Configure Metadata is set to True. Note: If you modify the metadata, ensure that it is in agreement with the query added.

Field

Description

Update Statement

An SQL statement used to update a record in the table. You can construct prepared SQL queries by using substitution variables (or parameters) of the form ?<fieldname> in the update query statement.

As you begin typing a query, the auto-suggest dropdown menu displays relevant keywords, table names, and column names that you can select from. To choose a column name from the dropdown menu, first type the table name followed by a period (.), which shows the list of available column names for that table.

If you are unfamiliar with the tables present in the database schema, press the CTRL + space key in the query editor to obtain auto-suggestion of all the tables and keywords present in the database schema.

Each substitution variable identifies an input parameter whose mapped value is substituted in the substitution variable at runtime. You can reuse the substitution variable for the same input parameter elsewhere in the query. The input fields in the Input tab of the activity are populated based on the SQL UPDATE statement. You must include the semicolon (;) at the end of the query. This activity expects an update query to end with a semicolon to indicate the end of the query. A missing semicolon at the end results in the query being unresponsive.

For now, only single table update queries are allowed.

Example of UPDATE query:
```
update SYSTEM.student set roll_no = ?roll_no where name like
?name;
```
For the above update query, roll_no(NUMBER) and name(VARCHAR) are in the Inputs tab as these fields are used as parameters. Also, the mapped values for the fields name and roll_no are substituted in the substitution variables ?name and ?roll_no at runtime.

Call Procedure and Call Functions Syntax:

With no parameters

Call  Procedure_Name( );

Select Function_Name( );

With prepared parameters

Call  Procedure_Name(?Param1 , ?Param2);

Select Function_Name(?Param1, ?Param2);

Manually Configure Metadata

Set the Manually Configure Metadata field to True to fetch table metadata manually. For more information, see Using Manually Configure Metadata Option.

Note: Schema retrieval may fail if nonstandard SQL is used.

Table Schema

Displays the metadata of the SQL update statement. You can modify the column metadata if Manually Configure Metadata is set to True.

Note: If you modify the metadata, ensure that it is in agreement with the query added.

Input

The Input tab displays the input schema of the activity as a tree structure. The schema varies according to the object that you selected on the Input Settings tab. You can provide the input values in the Flogo Connector for Oracle Database mapping input fields directly or use Mapper to map the input values to a field from the output of a preceding activity in the flow.

Output

The Output tab displays the output schema of the activity as a tree structure. The output is read-only. 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.