On this Page
| Table of Contents | ||||
|---|---|---|---|---|
|
Snap type: | Write | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap executes a SQL delete with the given properties. | ||||||||||||||||
| Prerequisites: | None | ||||||||||||||||
| Support and limitations: | Works in Ultra Pipelines. | ||||||||||||||||
| Account: | This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Oracle Account for information on setting up this type of account. | ||||||||||||||||
| Views: |
| ||||||||||||||||
Settings | |||||||||||||||||
Label | Required. 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 | 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.
Example: SYS | ||||||||||||||||
| Table name | Required. The table to execute the delete on.
| ||||||||||||||||
| Delete Condition (Truncates Table if empty) | 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.
Examples:
Default value: [None] | ||||||||||||||||
| Number of retries | 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. Example: 3 Default value: 0 | ||||||||||||||||
| Multiexcerpt include macro | |||||||||||||||||
| name | retries | page | File Reader|||||||||||||||
| Retry interval (seconds) | Specifies the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. Example: 10 Default value: 1 | ||||||||||||||||
|
| ||||||||||||||||
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. The second one will showcase error handling.
| Expand | ||
|---|---|---|
| ||
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.
|
.png?version=1&modificationDate=1489887587183&cacheVersion=1&api=v2)
| Expand | ||
|---|---|---|
| ||
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:
|
.png?version=1&modificationDate=1489887599627&cacheVersion=1&api=v2&height=250)
.png?version=1&modificationDate=1489887608233&cacheVersion=1&api=v2&height=400)
Downloads
| Multiexcerpt include macro | ||||
|---|---|---|---|---|
|
| Attachments | ||
|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|