Hi again. I actually now think there isn't anything wrong with the query, or basex, but the position I'm looking for is actually the same for every loop. Because it involved thousands of elements it was difficult to verify.

Thanks for your time,


On 12/01/2016 04:30 PM, Dirk Kirsten wrote:
Hi George,

you can't disable parts of the optimizer. I guess to be really able to
help you we will need to see the relevant part of the query and best an

However, if the problem exists in Saxon and BaseX it is quite probably a
problem with your query instead of the optimizers fault. I would be
rather surprised to see that Saxon and BaseX have exactly the same bug.


Reply via email to