I am reading the manual, too.

What is the difference between LINQ (Query.All<t>), Compiled (Query.Execute), and Future Queries? When is each appropriate? What are the consequences (e.g. performance) of each?

Updated at 13.01.2010 3:43:13

I asked this question after reading the first 2-3 pages... but the differences become very obvious as you continue reading. Sorry for being lazy =)

For others (as far as I understand):

1) Regularly query is executed on enumeration. 2) Compiled query is similar to a stored procedure... you can execute multiple queries that have different parameter values by reusing the compiled query (so that DO doesn't have to translate/compile your query every time). 3) Future queries allow you to create X number of queries... then have them executed in one batch (i.e. one round trip to DB).

Almost done reading manual... great job guys.

This thread was imported from our support forum. The original discussion may contain more detailed answer.

asked Jan 13 '10 at 01:49

ara's gravatar image


Yes, exactly - thanks for publishing a nice summary ;)

(Jan 13 '10 at 01:49) Alex Yakunin Alex%20Yakunin's gravatar image


I don't seem to be able to find any examples on how to pass parameters to Future Queries. Can someone help me here please?


(Jan 13 '10 at 01:49) Paul Sinnema Paul%20Sinnema's gravatar image

One Answer:

I have a tricky, but fast answer: I sent you the source today, so I can try to ask you to search for "ExecuteFuture" in our test projects :)

The example form Manual project: http://goo.gl/0iMh

answered Jul 28 '10 at 16:32

Alex%20Yakunin's gravatar image

Alex Yakunin

Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

powered by OSQA