Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <437491DC.6090807@zitting.name>
Date: Fri, 11 Nov 2005 14:43:08 +0200
From: Jukka Zitting <jukka@zitting.name>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
To: jackrabbit-dev@incubator.apache.org
Subject: Re: How to limit the nodes amount with xpath query returned
References: <620728fd0511062303o6f9ad543k@mail.gmail.com>
	 <436F1EE6.9080603@gmx.net> <620728fd0511072252l57635f37p@mail.gmail.com>
 <43706BCC.5080006@gmx.net> <43736ED9.4060609@zitting.name>
 <43745490.6020407@gmx.net>
In-Reply-To: <43745490.6020407@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

Marcel Reutegger wrote:
> that would work for a plain xpath query. but what about queries that
> have an order by clause? I'd expect something that allows me to limit
> the resultset after ordering.

Ah! I suppose you are right in this use case only being covered by a
proprietary extension. I don't see XPath supporting this anytime soon
(*), so perhaps JSR-283 could specify a limit/offset notation to extend
the order by notation specified in JSR-170.

(*) Full XPath 2.0 would actually be able to do this, but the hack is
both ugly and very slow. See
http://www.ximeco.org/Xime/XPathCanSortHlousek.pdf for the gory details. :-)

PS. I'll still make a Jira issue for the enhanced position() function.
It might come in handly every now and then.

BR,

Jukka Zitting