New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] XQuery bug on selecting nodes with last() #4824
Comments
I'm not very sure whether this is considered to be a bug or not, and might not be a common expression? Therefore it might not be of great importance or require a fix. Thanks! |
I can reproduce these results on 6.2.0. A bug is a bug! Thank you for your reports! My hunch is that this report is a variation of the earlier ones, and that solving them will solve this. |
It is definitely a valid predicate. I am just not sure what it actually does :) edit: Maybe it selects all elements, if there are less than 2 selected in the current XPath step. |
in saxon |
The results in Saxon are ... mixed |
Thank you very much! |
Christian Grün was so kind to explain to me what
This can only mean that eXistdb is currently not rewriting the shortcut |
Describe the bug
Given XML document:
(No index defined)
and XPath query:
Exist db returns empty result set
Expected behavior
Should return
as BaseX, Saxon and Oracle
To Reproduce
Context (please always complete the following information)
Additional context
conf.xml
? NoThe text was updated successfully, but these errors were encountered: