Differences

This shows you the differences between two versions of the page.

--- transformations:deletedbrowsbykeys [2021/07/19 06:02] – [Examples] craigt
+++ transformations:deletedbrowsbykeys [2026/09/22 06:06] (current) – Added additional settings, other minor changes roberto
@@ Line 15: / Line 15: @@
 \\
 =====Action settings=====
-Selecting the "Edit query" button opens the Query Editor for selecting the Connector and entering SQL queries.
 ^ Setting  ^ Description  ^
 |Connector<sup>*</sup>|Select or create a connector to the database.|
 |Table<sup>*</sup>|Select the table from the connected database containing the fields that will be used for comparison.|
 |Mode|Choose whether records with matching values will be deleted or retained (and non-matching rows are deleted).\\  Options:  //Delete rows where keys match// or //Delete rows where keys DON'T match//.|
-|Field mapping|Select the column in the current dataset ("This table"), and the associated field in the connected database ("Database\\ table"), containing the keys to be compared.  More than one set of fields may be selected by using the "Add more\\ matching columns" option.|
+|Disable removal of all rows when nothing matched|Available only in the //Delete rows where keys DON'T match// mode. Checked by default. If no row in the database table matches the keys, nothing is deleted and the action fails with the error "No matching values. Operation aborted." Without this option, all rows of the database table would be deleted.|
+|Field mapping|Select the column in the current dataset ("This table"), and the associated field in the connected database ("Database table"), containing the keys to be compared.  More than one set of fields may be selected by using the "Add more matching columns" option.|
 <sup>*</sup> Setting can be specified using a [[:parameters|parameter]].\\
 \\
 =====Remarks=====
-Under the hood, rows are deleted using SQL DELETE statement (with the WHERE statement from the query). The operation is //atomic// meaning that either all satisfying rows are successfully deleted, or nothing is deleted (in case of some failure).
+Under the hood, rows are deleted using SQL DELETE statement. The operation is //atomic// meaning that either all satisfying rows are successfully deleted, or nothing is deleted (in case of some failure).
 Note that this operation can't be undone -- database rows are deleted forever.
-Using a query in the action properties provides the convenience of previewing what rows will be deleted before actually deleting them.
 The key-matching process in this action is //not// case sensitive.