...
...
...
...
...
...
...
In this article
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Snap type:
Write
...
Description:
...
Overview
You can use this Snap to execute an SQL delete with the
...
specified properties.
...
Snap Type
The MySQL Delete Snap is a Write-type Snap.
Prerequisites
...
...
None
...
.
Support
...
for Ultra Pipelines
Works in Ultra
...
Limitations and Known Issues
| Multiexcerpt include macro | ||||
|---|---|---|---|---|
|
...
This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See MySQL Account for information on setting up this type of account.
...
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document
|
|
| WHERE clause for the delete condition. |
Output | Document
|
| Optional | 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 |
...
Settings
Label
...
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 while 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. |
Snap Settings
| Info |
|---|
|
Field Name | Field Type | Description |
|---|---|---|
Label*
| 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 |
...
Default Value: N/A | String/Expression/Suggestion | Specify the database schema name. |
|---|
...
If it is not defined, then the suggestion for the Table Name |
...
retrieves all tables names of all schemas. |
...
| ||
Table name*
|
|---|
...
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.
| Note |
|---|
Specify a valid WHERE clause for the delete condition. If you leave this field blank, the Snap truncates the table. |
...
people | String/Expression/Suggestion | Specify the table name to execute the delete on.
|
|---|
...
...
Delete condition (deletes all records from table if left blank) Default Value: N/A Examples:
| String/Expression | Specify the SQL WHERE clause of the delete statement. You can pass the delete condition via an upstream Snap or through the pipeline parameters. |
|---|
...
|
Default value: [None]
...
Number of retries
| Integer/Expression | Specify the maximum number of attempts to |
|---|
...
make to receive a response. The request is terminated if the attempts do not result in a response. |
...
Example: 3
...
Retry interval (seconds) |
|---|
...
| Integer/Expression | Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. |
|---|
...
|
...
Default Value: Execute only | Dropdown list |
|
|---|
...
Example
In this pipeline, we delete an entire table 'Disney' from the 'Snaplogic' schema.
| Note |
|---|
Give the delete conditions if a certain record or a column is to be deleted. You may also use the MySQL Select Snap to select a name of the record, and then give the delete condition in the MySQL Delete Snap to delete only those particular values from the table that satisfy the delete condition. |
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|