Page History
| Div | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Basically, stored procedures are modeled like static UML operations that can be called using a call operation action having the stereotype <<SQLAdapter>> as depicted in the activity diagrams below.
...
As input and output of stored procedures, the Bridge supports all simple base types.
| Noteinfo | ||
|---|---|---|
| ||
When specifying String objects as CLOB parameters, you have to mark them with tag nativeType=CLOB. |
| Noteinfo | ||
|---|---|---|
| ||
Please note that the user must be authorized to select data from the table |
...
You can find more information in the stored procedures example.
| Noteinfo | ||
|---|---|---|
| ||
You cannot run the example on the SQLite databases we deliver with the E2E Bridge tool set. If you have an Oracle database you could set up the stored procedures there and change the component diagram in the model to run it against your database. |
...
In the first case, the adapter iterates over the cursor and puts all results into the output array. In the second case, the adapter just returns the SQLHandle enabling the modeler to iterate over the cursor. This approach is to be preferred if the result set is big.
| Noteinfo | ||
|---|---|---|
| ||
You can name the parameter as you like. The name doesn't have to be result (as it is in the example) – only criteria are the direction, the stereoptype and the datatype. |
Overview
Content Tools