This a component for working with object-relational database management systems.
It works with the works with the
For integration-testing is needed to specify following environment variables:
Connection to DB:
CONN_USER_name- user login
CONN_PASSWORD_name- user password
CONN_DBNAME_name- DataBase name
CONN_HOST_name- DataBase host
CONN_PORT_name- DataBase port
namecan have these values:
MSSQL. For example:
You need to use following properties to configure credentials:
||compatible with MySQL Server 5.5, 5.6, 5.7 and 8.0|
||compatible with PostgreSQL 8.2 and higher|
||compatible with Oracle Database 8.1.7 - 126.96.36.199|
||compatible with Microsoft SQL Server 2008 R2 and higher|
Provide hostname of the server, e.g.
Database Name - Provide name of database at the instance that you want to interact with.
User - Provide a username that has permissions to interact with the Database.
Password - Provide a password of the user that has permissions to interact with the Database.
Configuration properties - Optional field. Provide a configuration properties for connections to the Database, e.g.
Configuration propertiesvalue may not be checked during Credentials Verification, so in case of using this field make sure that it contains correct input.
JDBC component includes the following triggers:
This trigger will execute an SQL query that returns multiple results, it has limitations on the query and suited only for SELECT type of queries. The trigger will remember last execution timestamp and let you build queries on it.
Get Rows Polling trigger
This trigger will execute select query from specified table with simple criteria of selected datetime or timestamp table. The trigger will remember last execution timestamp and let you build queries on it.s
JDBC component includes the following actions:
Execute custom query action
Action to execute custom SQL query from provided request string.
This action will execute insert query into the specified table. The action returns boolean value is execution insert successful or not.
Delete Row By Primary Key action
This action will execute delete query from specified table, as criteria can be used only PRIMARY KEY. The action returns an integer value that indicates the number of rows affected, the returned value can be 0 or 1 (a primary key is unique).
Execute stored procedure action
This action calls stored procedure from selected DB Schema and Stored procedure name.
Upsert Row By Primary Key action
This action will execute select command from specified table, as search criteria can be used only PRIMARY KEY, and execute insert command by PRIMARY KEY with specified field, if result does not found, else - action will execute update command by PRIMARY KEY with specified field. The action returns only one result row (a primary key is unique).
Only tables with one PRIMARY KEY is supported. You will see the message
Table has not Primary Key. Should be one Primary Key
, if the selected table doesn’t have a primary key. Also, you will see the message
Composite Primary Key is not supported
, if the selected table has composite primary key.
The current implementation of the action
Upsert By Primary Key doesn’t mark non-nullable fields as required fields at a dynamic metadata. In case of updating such fields with an empty value you will get SQL Exception
Cannot insert the value NULL into.... You should manually fill in all non-nullable fields with previous data, if you want to update part of columns in a row, even if data in that fields doesn’t change.
Execute stored proceduredoesn’t support:
MySQL: 40001, XA102