Documentation:OCLOperators ExecuteQueryPlan: Difference between revisions

OCLOperators ExecuteQueryPlan

Revision as of 15:37, 10 January 2022

When you have a collection of objects that 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.

What it does is to enter "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 92 days ago on 02/10/2024. What links here

Revision as of 15:35, 10 January 2022 (view source) Hans Karlsen (talk \| contribs) (Created page with "When you have a collection of objects that you do not know the fetch status of - and you are going to follow associationsm, or derive stuff that follows associations it is a g...")		Revision as of 15:37, 10 January 2022 (view source) Hans Karlsen (talk \| contribs) No edit summary Tag: Visual edit Newer edit →
Line 1:		Line 1:
	When you have a collection of objects that you do not know the fetch status of - and you are going to follow ~~associationsm~~, or derive stuff that follows associations it is a good idea to ask MDriven to ExecuteQueryPlan.		When you have a collection of objects that 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.

	What it does ~~then~~ is to enter "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 ~~factfinder~~ again - this way we can avoid 1000 single fetches and end up with 2-3 large fetches instead.		What it does is to enter "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.