Description
Class name: com.ebd.hub.datawizard.util.DBProcCustomResponse
Configuration: Done directly with a string in field "Additional parameters".
This class is able to call a database procedure. The field "Additional parameters" requires the procedure call with parameter placeholder using the syntax @<index>:<abbreviation data type>@ (e.g. @1:i@, index starts at 1.) and the database alias, separated by a semicolon.
If the procedure requires parameters, the values of those parameters must follow the database alias, also separated by semicolons. It depends on the database system if an SQL keyword (e.g. CALL or EXECUTE) is needed for the procedure call.
<procedure call>;<database alias>;[<parameter value>] |
List of data types:
Abbreviation | Data type |
|---|---|
i | Integer |
f | Float |
r | Real |
d | Date |
t | Timestamp |
s | String |
l | Long |
v | Boolean |
b | Blob |
x | Textream |
Examples
MySQL
To call a procedure TextProc the configuration could be like this:
CALL TestProc(@0:i@);testcenter;@var_variable@ |
In this case, the variable var_variable is of type Integer.
If an additional parameter should be passed on with type String, the configuration would be:
CALL TestProc(@0:i@,@1:s@);testcenter;@var_variable@;hello |
MSSQL
To call an MSSQL procedure called "EDIMessage_updatestatus", the configuration could be:
EXEC edimessage_updatestatus @0:i@,@1:s@;test;@var__id@;@var__state@ |
In this example, the variables var__id (as Integer) and var__state (as String) will be transferred.
Oracle
To call a Oracle procedure called "import.data", the configuration could be:
{call import.data(@0:s@)};test;@var__file@ |
The variable "var__file" is of type "String".