Insert Table
Inserts data into an Oracle database table.
Common Properties
- Name - The custom name of the node.
- Color - The custom color of the node.
- Delay Before (sec) - Waits in seconds before executing the node.
- Delay After (sec) - Waits in seconds after executing node.
- Continue On Error - Automation will continue regardless of any error. The default value is false.
info
If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.
Inputs
- Connection Id - The ID of the database connection to use.
- Transaction Id - The ID of the transaction to use (optional).
- Table Name - The name of the database table to insert data into.
- Table Data - The data to insert, provided as a table structure.
Options
- Replace - If true, uses INSERT OR REPLACE statement instead of regular INSERT.
How It Works
The Insert node inserts data into an Oracle database table by:
- Validating the provided Connection Id and Table Name
- Looking up the connection and transaction in the shared dictionaries
- Creating an INSERT command for each row in the table data
- Executing the INSERT command for each row
- Using a transaction if a Transaction Id is provided
Requirements
- An active database connection established with the Connect node
- A valid table name that exists in the database
- Table data in the correct format
- Appropriate permissions to insert data into the specified table
Error Handling
The node will return specific errors in the following cases:
- Empty or invalid Connection Id
- Empty or invalid Table Name
- Connection ID not found in the connections dictionary
- Transaction ID not found in the transactions dictionary (when provided)
Usage Notes
- The Connection Id must be valid and correspond to an active connection
- If a Transaction Id is provided, it must be valid and correspond to an active transaction
- The Table Data should be structured as a table with rows and columns
- When using the Replace option, existing rows with matching primary keys will be replaced
- For large datasets, consider using batch operations for better performance