![[Important]](https://bs-docs2.boost.space/wp-content/themes/bsdocs/docs-parser/HTML/css/image/important.png)
The PostgreSQL modulesThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More let you execute your custom logic directly in your database server through functionsFunctions you can use in Boost.space Integrator - create, update, delete, get, search.. Boost.spaceCentralization and synchronization platform, where you can organize and manage your data. More IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. More loads interface of input and output parameters dynamically so each parameter can be mapped individually.
Here is a sample SQL statement that creates a functionFunctions you can use in Boost.space Integrator - create, update, delete, get, search. that just simply inserts the values passed in the three parameters into a table:
CREATE OR REPLACE FUNCTION insert_record_from_Boost.space Integrator(_name character varying,_email character varying, _phone character varying) RETURNS void LANGUAGE 'plpgsql' AS $BODY$ BEGIN INSERT INTO contacts (name, email, phone) VALUES (_name, _email, _phone); END; $BODY$;
To learn more about creating functions, see PostgreSQL documentation.
Make sure the account you’re using to connect to your database has read access to ‘information_schema.routines’ and ‘information_schema.parameters’ tables.
Boost.space Integrator will make connections to your database from specifc IP addresses. Our servers are set up with valid PTR recordsOne row in the Boost.space database. These are individual rows under spaces in each module. For example single products, but not their variants. More so you can easily restrict access by allowing %.make.com.
This errorService is unavailable due to a failure, a service responds with unexpected data or the validation of input data fails. More occurs when you modify the same data using multiple modules. It is caused by SQL transactions.
When any SQL moduleThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More is executed then it starts the transaction (1) and the transaction is finished after the scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. More is fully executed.If another module tries to access the same data used in another unfinished transaction (1) then it has to wait until the previous transaction (1) is finished – but it never happens because the first transaction (1) will be finished after the scenario is finished.
Solution
Turn on Auto-commit. It finishes (commits) every transaction immediately after the module execution is done.
-
Open Scenario settings.
-
Enable theAuto commitThe Auto commit option defines how Boost.space Integrator processes data transactions. Enabling Auto commit switches all operations to the commit phase. In the case of an error, data commits immediately and you cannot restore any lost data. checkbox.
-
Confirm the settings dialog by clicking the OK button.
