Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of aklimets@adobe.com designates
 64.18.1.27 as permitted sender)
From: Alexander Klimetschek <aklimets@adobe.com>
To: "users@jackrabbit.apache.org" <users@jackrabbit.apache.org>
Date: Tue, 25 Oct 2011 22:20:13 +0100
Subject: Re: AW: How do I get the total size of nodes/rows from a QueryResult
Thread-Topic: AW: How do I get the total size of nodes/rows from a
 QueryResult
Thread-Index: AcyTW+ak2uNsw70aRq6/NlEj5GkFew==
Message-ID: <CACCF310.8F732%aklimets@adobe.com>
In-Reply-To: <DD48F4D5B13C134A81F9FB51AD43DE21027F6F16@email.innoimm.local>
Accept-Language: de-DE, en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

On 25.10.11 18:06, "Sascha.Theves@bosch-si.com"
<Sascha.Theves@bosch-si.com> wrote:

>> Use the getSize() method of the returned node or row iterator.
>
>I think that returns the size of elements in the iterator and that is
>hopefully not the complete size if I used the limit and offset options...

Yes, I also think it is the actual result "window" size (if given), but
not the total. (But I am not 100% sure).

>I used an XPath query before switching to jackrabbit 2.2.9 but I thought
>I should change my query to SQL2 because xpath is deprecated now.

It is deprecated in the spec - but most Jackrabbit based systems use xpath
heavily so it is not going away soon. SQL2 on the other hand is still very
young - and while having some new features, such as joins, it is not as
optimized and proven as Xpath or SQL1.

(We should really put that in a FAQ).

>So what is your recommendation now? Should I switch to SQL2? What about
>the total size then? Or should I still use xpath? I am currently
>switching because it seems that my xpath queries do not work any longer.
>A lot of tests do fail now... I have to track this down but it seems that
>I run into another backward incompatibility issue here...

I guess it's only that getSize() returns -1 for you now in most cases (if
you come from Jackrabbit 1.x), as that is an optimization in the engine.
To force a result, use the orderby @jcr:score trick mentioned by Ard.

You can't be using limit & offset with Jackrabbit 1.x and Xpath...

Cheers,
Alex

--=20
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel