Table Exists
Description
The Table exists action verifies that a specified table exists on a database.
You must provide a connection and the table name.
Hop returns a True or False value depending on whether the table exists.
Suppose you have an external system that creates a summary table or yesterday’s data extract.
The external system may not have performed the action yet, so you set up a polling piece that waits for the staged data to arrive in the database.
There is no point in processing the workflow until the data is available, so you can use this workflow action as a semaphore that polls the database to determine whether or not the table exists.
Options
| Option | Description |
|---|---|
Action name |
The name of the workflow action. |
Connection |
The connection to use |
Schema name |
The schema name if applicable to your database |
Table name |
The name of the database table to check |
Result
What this action passes on to the next action. See Action results for how results travel through a workflow.
| Result | Value |
|---|---|
True |
The table exists, with 0 errors. |
False |
The table doesn’t exist: the number of errors is 0. When the connection is empty or can’t be opened, the number of errors is 1. |
Result files |
Passed on unchanged. |
Result rows |
Passed on unchanged. |
| A Connection that doesn’t exist in the project also gives false with 0 errors, and nothing is logged: the same result as a table that doesn’t exist. |