[Dev] Chandler Query Proposal 0.1

[Katie Capps Parlante]

Katie Capps Parlante wrote:
>>    8. It must be possible to determine the result set size of the
>>       previous exeuction of a query (this really means query over a
>>       particular collection(s)
> 
> This requirement seems like one of the more contentious requirements. In 
> a perfect world, the application knows the size of the result set and 
> can make use of it in the api. In a perfect world, the implementation 
> doesn't have to know the size of the result set so that it can be 
> efficient. Perhaps what we're looking for is some way of getting a hint 
> to the ui about the size of the result set if possible.

I made a typo in the section above that might cause confusion. What I 
meant to say:

 > a perfect world, the application knows the size of the result set and
 > can make use of it in the *ui*. (not the api)

The point is that we can write the application code so that it can 
handle an iterator and not know the size of the result set, that is not 
so much a problem. The problem is that we can provide a nicer ui if we 
have some clue as to the size of the result set.

Cheers,
Katie