Hi, On Thu, Sep 13, 2012 at 9:56 AM, Thomas Mueller <[email protected]> wrote: > [...] When I opened OAK-300, it was for the JCR API implementation. [...]
Ah, I see, sorry for confusing the matter. For the JCR API I'd simply start by ensuring that getSize() will always return the correct size if the result set has fewer than something like 1000 entries. That should cover most practical cases and existing client code without requiring new query syntax or other API extensions. > If getSize(int max) is just in the Oak API but not > available for the end user, then we didn't really gain much :-) If we come up with a better API design in oak-core, that'll be a good candidate for inclusion in JCR 2.1. BR, Jukka Zitting
