Hans Karlsen (talk | contribs) (Created page with "A way to switch from ocl to oclps in any expression") |
No edit summary |
||
| (12 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
<message>Write the content here to display this box</message> | |||
OCLOperator PSEvalValue makes it possible to use oclPS in any OCL expression. | |||
Expression template: | |||
SomeClass.PSEvalValue(SomeClass.allinstances->select(x|x.name=vWhatever)->size,dependon) | |||
Using this, you can "reach into" the database from OCL and action-language (EAL). | |||
'''Note!''' PSEval doesn't subscribe to the value from the DB. To make the operator auto-updating, provide an expression in "dependon" that, when changed, should also rerun the PSEval expression. This can, for example, be a timer. | |||
'''Warning!''' Remember that using PSEval means that no changes to the result set content will be fetched automatically. This breaks the very nice subscription feature built into the framework for that data. | |||
For example, this expression from a method has "userName" as a parameter: | |||
SysAsyncTicket.PSEvalValue(SysAsyncTicket.allInstances->select(at|at.Error.notNull)->size, Calendar.Now).asString | |||
The expression above will execute the '''select count(*)''' on the table SysAsyncTicket with a where statement filtering on '''Error IS NOT NULL''' and then getting the value (number of rows). In the [[BaseApp]] model, Calendar.Now updates every minute, which makes the count reevaluate as long as this value is used. | |||
Always remember that your SQL-server might also need indexes and other performance settings to execute your expression efficiently. | |||
See also: [[OCLOperators Sqlpassthrough|Sqlpassthrough]], [[OCLOperators PSEval|PSEval]], [[Documentation:OCLOperators PSEvalTuples|PSEvalTuples]] | |||
[[Category:OCLOperators]] | |||
{{Edited|July|12|2024}} | |||
Latest revision as of 05:06, 27 June 2024
OCLOperator PSEvalValue makes it possible to use oclPS in any OCL expression.
Expression template:
SomeClass.PSEvalValue(SomeClass.allinstances->select(x|x.name=vWhatever)->size,dependon)
Using this, you can "reach into" the database from OCL and action-language (EAL).
Note! PSEval doesn't subscribe to the value from the DB. To make the operator auto-updating, provide an expression in "dependon" that, when changed, should also rerun the PSEval expression. This can, for example, be a timer.
Warning! Remember that using PSEval means that no changes to the result set content will be fetched automatically. This breaks the very nice subscription feature built into the framework for that data.
For example, this expression from a method has "userName" as a parameter:
SysAsyncTicket.PSEvalValue(SysAsyncTicket.allInstances->select(at|at.Error.notNull)->size, Calendar.Now).asString
The expression above will execute the select count(*) on the table SysAsyncTicket with a where statement filtering on Error IS NOT NULL and then getting the value (number of rows). In the BaseApp model, Calendar.Now updates every minute, which makes the count reevaluate as long as this value is used.
Always remember that your SQL-server might also need indexes and other performance settings to execute your expression efficiently.
See also: Sqlpassthrough, PSEval, PSEvalTuples