Differences

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

--- transformations:selectdbrowsbykeys [2017/05/02 23:10] – created dmitry
+++ transformations:selectdbrowsbykeys [2021/04/08 23:49] (current) – craigt
@@ Line 1: / Line 1: @@
-===== Select matching database rows =====
+{{ transformations:SelectDbRowsAction.png}}
+======SELECT MATCHING DATABASE ROWS======
+Category: Import / Database\\
-Selects rows from a database table where a combination of key fields matches a combination of key fields in EasyMorph table.
+\\
+=====Description=====
+Selects rows from a database table where a combination of key fields matches a combination of key fields in an EasyMorph table. \\
-Under the hood the transformation creates a temporary table in the target database, uploads key field combinations into it and performs SELECT..WHERE ..EXISTS statement. After the statement is executed the temporary table is deleted.
+\\
+=====Use cases=====
+This action can be used for //pre-filtering//. Pre-filtering means that instead of loading an entire dataset and then filtering it, only a few fields are loaded (using [[transformations:importsql|Import from database]]) that are necessary for filtering, as well as primary/foreign keys (i.e. IDs). When imported, these fields can be filtered by any of various EasyMorph transformations. The resulting subset of IDs is used to fetch full records from the source dataset using the //Select matching database rows// action. Pre-filtering can be helpful when the source table is large and doesn't entirely fit in RAM.
-**Use cases**
+Another use case is //cross-source filtering// which means importing database records having IDs that are obtained from another data source (e.g. text file or spreadsheet).\\
-This transformation can be used for //pre-filtering//. Pre-filtering means that instead of loading entire dataset and then filtering it, only a few fields are loaded (using [[transformations:importsql|Import from database]]) that are necessary for filtering, as well as primary/foreign keys (i.e. IDs). When imported these fields can be filtered by means of various EasyMorph transformations. The resulting subset of IDs is used to fetch full records from the source dataset using "Select matching database rows" transformation. Pre-filtering can be helpful when source table is large and doesn't fit RAM entirely.
+\\
+=====Remarks=====
-Another use case is //cross-source filtering// which means importing database records which IDs are obtained from another data source (e.g. text file or spreadsheet).
+Under the hood, the action creates a temporary table in the target database, uploads key field combinations into it, and performs a SELECT..WHERE..EXISTS statement. After the statement is executed the temporary table is deleted.\\
+\\
+=====See also=====
+  *[[transformations:importsql|Import from database]]