We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given this XML document:
<T1 id="1">1</T1>
and this XPath query:
//*[not((@id * (-1)) > (-2))]
BaseX gives result
Should return empty result set as Saxon & ExistDB.
Using BaseX Client:
create database test
put test.xml path/to/file
xquery //*[not((@id * (-1)) > (-2))])
<T1 id="1">1</T1>//*[not((@id * (-1)) > (-2))])
No response
BaseX version: 10.4 on Windows (Also reproduced on the latest stable snapshot 10.5 provided in https://files.basex.org/releases/latest/)
The text was updated successfully, but these errors were encountered:
6013836
Thanks for the observation. A new stable snapshot with the bug fix has been uploaded.
Sorry, something went wrong.
Thanks for the quick fix!
No branches or pull requests
Description of the Problem
Given this XML document:
and this XPath query:
BaseX gives result
Expected Behavior
Should return empty result set as Saxon & ExistDB.
Steps to Reproduce the Behavior
Using BaseX Client:
create database test
put test.xml path/to/file
xquery //*[not((@id * (-1)) > (-2))])
(Note: Directly executing
<T1 id="1">1</T1>//*[not((@id * (-1)) > (-2))])
does not trigger the bugDo you have an idea how to solve the issue?
No response
What is your configuration?
BaseX version: 10.4 on Windows
(Also reproduced on the latest stable snapshot 10.5 provided in https://files.basex.org/releases/latest/)
The text was updated successfully, but these errors were encountered: