Michael Sick wrote: > Niclas Hedhman wrote: >>> On Tue, Apr 29, 2008 at 9:03 PM, Rickard Öberg <[EMAIL PROTECTED]> > wrote: >>> I mean size(), find() and iterator() could all trigger the query, but >>> there is one small difference... >>> >>> size() need to return the number of objects that a non-bounded (with >>> first/max) query would return, whereas the find() and iterator() only >>> deal with the (potentially) bounded query. For simple queries, a good >>> backend will be very fast for a SELECT count(*) from Abc where age > >>> 25; > >> Rickard: Yeah, I guess there is no other way than to simply execute the > query on >> those three operations, with the semantics as you outlined. That would >> make it very easy to implement paging views at least. >> Anyone see any problems with that semantics? > > With the disclaimer that I'm a total outsider, non-contributor, I think that > count() would be more clear in intentions than size(). In both its noun and > verb form it makes sense.
That makes total sense, and in retrospect it's interesting how we got stuck with size() really :-) /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
