Delete Data (G Dataflow)

Reference to an ADO Connection object. Connection objects represent a connection with a data source, including methods to open and close a connection with a database, which database to connect with, and the level of isolation for database transactions.

Name of the table in the database from which to select data.

You can specify multiple tables by using commas as the delimiter.

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error
If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

SQL clause that filters selection criteria. The clause appends to the end of a delete statement. Wire an empty string to this input to delete all tables.

Reference to an ADO Connection object. Connection objects represent a connection with a data source, including methods to open and close a connection with a database, which database to connect with, and the level of isolation for database transactions.

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error	error in contains an error
If no error occurred before the node runs, the node begins execution normally. If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.	If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.