Documentation:OCLOperators ExecuteQueryPlan: Difference between revisions

OCLOperators ExecuteQueryPlan

Revision as of 22:21, 16 June 2024

Write the content here to display this box

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 95 days ago on 06/17/2024. What links here

Revision as of 15:38, 10 February 2024 (view source) Wikiadmin (talk \| contribs) (Automatically adding template at the end of the page.) ← Older edit		Revision as of 22:21, 16 June 2024 (view source) Wikiadmin (talk \| contribs) (Adding message template to the top of the page) Newer edit →
Line 1:		Line 1:
			{{message\|Write the content here to display this box}}
	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.		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.