Documentation:OCLOperators ExecuteQueryPlan: Difference between revisions

OCLOperators ExecuteQueryPlan

Latest revision as of 05:54, 20 January 2025

This page was created by Hans.karlsen@mdriven.net on 2022-01-10. Last edited by Edgar on 2025-01-20.

When you have a collection of objects you do not know the fetch status of and you are going to follow associations or derive stuff that follows associations, it is a good idea to ask MDriven to ExecuteQueryPlan.

It enters "fact-finder-mode", running your expressions in the ViewModel in a harness - looking at what data WOULD be fetched - then it fetches that data and runs the fact-finder again. This way, we can avoid 1000 single fetches and end up with 2-3 large fetches instead.

@@ Line 1: / Line 1: @@
+<message>Write the content here to display this box</message>
 When you have a collection of objects you do not know the fetch status of and you are going to follow associations or derive stuff that follows associations, it is a good idea to ask MDriven to ExecuteQueryPlan.
 It enters "fact-finder-mode", running your expressions in the ViewModel in a harness - looking at what data WOULD be fetched - then it fetches that data and runs the fact-finder again.  This way, we can avoid 1000 single fetches and end up with 2-3 large fetches instead.
 [[Category:OCLOperators]]
+{{Edited|July|12|2025}}