Description of the Problem
Given this XML document:
and this XPath query:
//*[not((@id * (-1)) > (-2))]
BaseX gives result
Expected Behavior
Should return empty result set as Saxon & ExistDB.
Steps to Reproduce the Behavior
Using BaseX Client:
- Create database
create database test
- Insert XML file into database
put test.xml path/to/file
- Execute XPath query
xquery //*[not((@id * (-1)) > (-2))])
(Note: Directly executing <T1 id="1">1</T1>//*[not((@id * (-1)) > (-2))]) does not trigger the bug
Do 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/)
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 testput test.xml path/to/filexquery //*[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/)