Querying in RavenDB is both similar and dissimilar to the sort of queries that you are familiar with from RDBMS. For example, in RavenDB, it is crazily cheap to find out count(*). And then there is the notion of potentially stale queries that we need to expose.
Following the same logic as my previous post, I want to have an easy way of exposing this to the user without making it harder to use. I think that I found a nice balance here:
RavenQueryStatistics stats; var results = s.Query<User>() .Customize(x=>x.WaitForNonStaleResults()) .Statistics(out stats) .Where(x => x.Name == "ayende") .ToArray();
The stats expose some additional information about the query:
You can use those to decide how to act.
But I have to admit that, like in the MultiQuery case with NHibernate, the real need for this was to be able to do paged query + total count in a single remote request.