OCLOperators PSEval
No edit summary
(Replacing message template with parser tag)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Makes it possible use oclPS in any OCL expression.
<message>Write the content here to display this box</message>
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
Expression template:
  SomeClass.PSEval(SomeClass.allinstances->select(x|x.name=vWhatever),maxfetch,offset,dependon)
  SomeClass.PSEval(<ps-expression>,maxfetch,offset,<dependon>)
Using this you can "reach into" the database from OCL and action-language (EAL)
'''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 don't subscribe on 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.


For example this expression from a method having "userName" as a parameter
'''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,<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 be able to execute your expression efficient.
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]]
See also: [[OCLOperators Sqlpassthrough|Sqlpassthrough]], [[OCLOperators PSEvalValue|PSEvalValue]], [[Documentation:OCLOperators PSEvalTuples|PSEvalTuples]]
[[Category:OCLOperators]]
{{Edited|July|12|2024}}

Latest revision as of 07:48, 17 June 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

This page was edited 95 days ago on 06/17/2024. What links here