Re: numeric predicates revisited

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: numeric predicates revisited

Hi Michael,

your example made the bug very obvious, thanks. The [n] version indeed
processed the nodes according to eXist's internal numbering scheme
(i.e. level-first). [position()=n] uses an iterator instead, which
transparently reorders the node set in document order.

I fixed the bug in cvs today.


On 9/2/05, Michael Beddow <[hidden email]> wrote:
> Coming back to the problem of numeric attribute values, I have revised and
> rerun my earlier test, using a current CVS build.
> To recap, the problem is that abbreviated-form numeric predicate values [N]
> are incorrectly interpreted, whereas the unabbreviated form [position()=N]
> is handled correctly.

SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement *
Exist-open mailing list
[hidden email]