DB Connector
Last updated
Last updated
This connector allows to perform operations with external or internal (provisioned through ProcessMIX) relational databases (RDBMS): querying, inserting, updating, and deleting data stored in the database tables.
PostrgreSQL
Oracle 11g
Name - refers to the unique identifier. (must consist of letters (A-Z or a-z), digits (0-9), underscores (_), or dollar signs ($). However, a class name cannot start with a digit and dollar sign ($))
Database type - defines type of database to connect
- address of the database to connect.
User - username
Password - password
All settings should be defined as . This enables the redefinition of values for new deployments.
URL is a string that depends on type of database to connect with.
URL structure:
jdbc:db_type://server:port/db_name?currentSchema=schema_name
jdbc - system uses Java drivers to connect to databases. Don't modify this prefix
db_type - database type
server - database server address
port - server port
db_name - database name
schema_name - (OPTIONAL) define schema to restrict access inside query builders
Example:
jdbc:postgresql://dbpublic.cloud.domain.com:5455/ewallet?currentSchema=public
There are two types of queries:
A transaction is a set of operations for working with a database (DB), combined into one atomic bundle. It is used when it is important to perform a set of actions altogether, if each separate action does not make any sense without the others, or if the data in different places must be in a consistent state.
If at least one operation from the transaction fails as an error or exception, the system cancels and undoes ("rolls back") every database operation completed so far, restoring the data to its previous stable state.
Find more information please refer to the following help sections:
- SQL should be defined during the design phase.
- SQL should be defined at runtime.
- allows to call stored procedures