OCLOperators ExecuteQueryPlan
No edit summary
(Automatically adding template at the end of the page.)
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
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.
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]]
[[Category:OCLOperators]]
{{Edited|July|12|2024}}

Latest revision as of 15:38, 10 February 2024

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.

This page was edited 91 days ago on 02/10/2024. What links here