When you define and use a custom Transaction object to call remote stored procedures in your application, the features supported depend on the DBMS to which your application connects. Stored procedures are not supported in UltraLite databases.
Result sets
You cannot use the remote procedure call
technique to access result sets returned by stored procedures. If
the stored procedure returns one or more result sets, PocketBuilder
ignores the values and returns the output parameters and return
value.
If your stored procedure returns a result set, you can use the embedded SQL DECLARE Procedure statement to call it. For information about the DECLARE Procedure statement, see the chapter on SQL statements in the online Help.
If your application connects to an SQL Anywhere database, you can use the following features:
IN, OUT, and IN OUT parameters, as shown in Table 16-4.
Parameter |
What happens |
|---|---|
IN |
An IN variable is passed by value and indicates a value being passed to the procedure. |
OUT |
An OUT variable is passed by reference and indicates that the procedure can modify the PowerScript variable that was passed. Use the PowerScript REF keyword for this parameter type. |
IN OUT |
An IN OUT variable is passed by reference and indicates that the procedure can reference the passed value and can modify the PowerScript variable. Use the PowerScript REF keyword for this parameter type. |
Blobs as parameters. You can use blobs that are up to 32,512 bytes long.
