In this article
Table of Contents | ||||
---|---|---|---|---|
|
Overview
You can use this Snap to execute a SQL delete as per the configured properties.
Upcoming
Multiexcerpt include macro | ||||||||
---|---|---|---|---|---|---|---|---|
|
Snap Type
The Oracle Delete Snap is a WRITE-type Snap.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| The records to be deleted. |
Output | Document |
| NA | This Snap has at most one document output view. If an output view is available, then the original document that was used to create the statement will be output with the status of the delete executed. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. |
Field Name | Field Type | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Label Default Value: Oracle Delete | String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | ||||||||||||||||
Schema name
| String/Expression/Suggestion | The database schema name. In case it is not defined, then the suggestion for the Table Name will retrieve all tables names of all schemas. The property is suggestible and will retrieve available database schemas during suggest values.
| ||||||||||||||||
Table name
| String/Expression/Suggestion | Required. The table to execute the delete on.
| ||||||||||||||||
Delete condition (deletes all records from table if left blank) Default value: N/A Examples: Without using expressions
Using expressions
| String/Expression | This is an expression property to specify the SQL WHERE clause of the delete statement. The delete condition may also be passed via an upstream Snap or through the pipeline parameters.
| ||||||||||||||||
Number of retries Example: 3 Default value: 0 | Integer/Expression | Specifies the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. | ||||||||||||||||
Retry interval (seconds) Example: 10 Default value: 1 | Integer/Expression | Specifies the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. | ||||||||||||||||
|
|
Examples
Following are the two examples, the first one using a conditional update of one of the values that then gets merged into the data using the Oracle - Merge Snap.
In this example, we have a table named STUDENT that stores students' scores. It has 3 columns: ID, NAME and SCORE. Now we want to delete all the student records that have same scores with Adam's, so we built this pipeline:
The Oracle - Select Snap finds the row whose NAME is 'Adam', and pass the row's data to Oracle - Delete Snap:
Then the Oracle - Delete Snap will delete all the rows that has the same score as Adam's. We use $SCORE to retrieve data of SCORE Column passed from Oracle - Select Snap.
Error Handling
The second one will showcase error handling.
This example will show the error handling of the Snap.
We use the same pipeline as the one in Example #1 and let error messages route to error view:
We set the Delete condition property to "Score = $NAME", which is supposed to cause a type mismatch error since column SCORE is of type NUMBER while column NAME is of type VARCHAR2:
Here is the error message that is routed to error view:
Downloads
Multiexcerpt include macro | ||||
---|---|---|---|---|
|
Attachments | ||
---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|