No edit summary |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
SomeClass.PSEval(<ps-expression>,maxfetch,offset,<dependon>) | SomeClass.PSEval(<ps-expression>,maxfetch,offset,<dependon>) | ||
'''Note!''' PSEval doesn't subscribe to sets from 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. | '''Note!''' PSEval doesn't subscribe to sets from 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. | |||
'''Note!''' Offset is 0-based. | |||
Example: | Example: | ||
| Line 10: | Line 14: | ||
SysUser.PSEval(SysUser.allinstances->select(su|su.Username=userName),2,0,<nowiki>''</nowiki>) | SysUser.PSEval(SysUser.allinstances->select(su|su.Username=userName),2,0,<nowiki>''</nowiki>) | ||
Always remember that your SQL-server might also need indexes and other performance settings to execute your expression efficiently. | Always remember that your SQL-server might also need indexes and other performance settings to execute your expression efficiently. | ||
'''Note!''' The offset parameter should almost always be 0, if not used to show a seconds page in a pagination or similar. | |||
See also: [[OCLOperators Sqlpassthrough|Sqlpassthrough]], [[OCLOperators PSEvalValue|PSEvalValue]], [[OCLOperators PSEvalTuples|PSEvalTuples]] | See also: [[OCLOperators Sqlpassthrough|Sqlpassthrough]], [[OCLOperators PSEvalValue|PSEvalValue]], [[OCLOperators PSEvalTuples|PSEvalTuples]] | ||
[[Category:OCLOperators]] | [[Category:OCLOperators]] | ||
{{Edited|July|12|2024}} | |||
Latest revision as of 21:30, 3 May 2024
The OCLOperator PSEval makes it possible to use oclPS in any OCL expression. Using this, you can "reach into" the database from OCL and action-language (EAL).
Expression template:
SomeClass.PSEval(<ps-expression>,maxfetch,offset,<dependon>)
Note! PSEval doesn't subscribe to sets from 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.
Note! Offset is 0-based.
Example:
Uppdrag.PSEval(self.Uppdrag->select(u|u.Aktivt)->orderDescending(u|u.Startdatum), 1000, 0, self.Uppdrag)
For example, this expression from a method has "userName" as a parameter:
SysUser.PSEval(SysUser.allinstances->select(su|su.Username=userName),2,0,'')
Always remember that your SQL-server might also need indexes and other performance settings to execute your expression efficiently.
Note! The offset parameter should almost always be 0, if not used to show a seconds page in a pagination or similar.
See also: Sqlpassthrough, PSEvalValue, PSEvalTuples