Fix broken linq count() processing on anything that is pagged like journals. Count is defined as the nuber of records, and cannot be pagged.
Fix linq count() to match stanadard, not massed up version..
Count cannot be paged, this is very basic..
ray
shared this idea
-
Dave Conlin
commented
I agree that the ability to find out how many things there are in total is really important.
When you're batching/showing a user a large amount of information, it's really important to be able to give them an idea of the scale of the operation (progress bars, page numbers etc)
Not sure that the implementation has to be "make the c# api return the right value for count", you could return some information as part of the query about the query stats. RavenDB is a pretty good example of how to make the second one work pretty well:
http://ravendb.net/docs/client-api/querying/paging
You could just slip in some extra information in the xml doc, outside the results list.
Anyway, implementation isn't that important, but I do think that when you return paginated results, it's important to be able to find out how many there are, not just say "carry on getting new pages until there are none left"