| Code Block | ||||
|---|---|---|---|---|
| ||||
FUNCTION xpfExecuteQuery (queryHandle : INTEGER; argument1, ..., argumentN : GENERIC) -- arguments to actual called query modelId queryFunctionValue : GENERIC; FUNCTION xpfExecuteQueryEx (dataModelId : GENERIC; -- optional. Default is callers actual data model argument queryHandle : INTEGER; argument1, ..., argumentN : GENERIC) -- arguments to actual called query queryFunctionValue : GENERIC; FUNCTION xpfExecuteQueryBN (expressSchemaName : STRING; querySchemaName : STRING; queryFunctionName : STRING; argument1, ..., argumentN : GENERIC) -- arguments to actual called query queryFunctionValue : GENERIC; FUNCTION xpfExecuteQueryEXBN (dataModelId : GENERIC; -- optional. Default is callers actual data model expressSchemaName : STRING; querySchemaName : STRING; queryFunctionName : STRING; argument1, ..., argumentN : GENERIC) -- arguments to actual called query queryFunctionValue : GENERIC; Related functions: ================== FUNCTION xpxSetVmTargetModelBN (repositoryNameOrRepositoryId : GENERIC; modelNameOrModelId : GENERIC; modelAccessMode : INTEGER); -- LATER: xpxAddModelToActiveTransaction if xpxRW FUNCTION xpxSetVmTargetModel (modelId : GENERIC; modelAccessMode : INTEGER; -- LATER: xpxAddModelToActiveTransaction if xpxRW |
...
See also:
...
| Include Page | ||||
|---|---|---|---|---|
|
The argument “modelId” is optional, i.e., it is not “necessary” for the calling function to set the actual target data model for the called function. The data model (xpxTargetModelId) can be set in the called function itself by invoking one of the following two functions:
Note: An exception (error) will be raised when one of these two above listed functions are called within an “open” FROM statement. The xpfExecuteQuery function has an argument called “queryHandle”. In general, the concept “handles” is introduced in EDMvm to boost performance. Until now, items like local variables, global variables, functions, etc., has been search for using linked lists, but using handles , the actual handle gives a direct “address” to the actual item. A handle is only valid within one EDMvm session. Simplified, a handle is similar to “an open file descriptor”, i.e., it must be retrieved in each session of a program,
The following functions are introduced for retrieving handles:
The xpfGetFunctionHandleBN and the xpfGetFunctionHandle functions can be used to get the “function handle” to any function in a query schema, not only query functions.
Arguments
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Return Value
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Options
...
Example
...
<example missing>
See also
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|