Thanks, Tim,

That was helpful: You came across a hidden bug that was introduced three years ago (and which was probably triggered by some newer optimizations). The bug has been fixed [1,2].

Best,
Christian

[1] https://github.com/BaseXdb/basex/issues/2261
[2] https://files.basex.org/releases/latest



On Wed, Nov 22, 2023 at 4:10 PM Thompson, Timothy <timothy.thompson@yale.edu> wrote:

Hello,

 

In BaseX 11.0 beta, I’m encountering a strange error. I’ve created a gist that illustrates the behavior: https://gist.github.com/timathom/7fd44b43de1fa72162cd59cf755c3d91.

 

I have a series of maps that I want to check against a lookup index and then filter the results. I’m setting a Boolean variable that only seems to get applied if I reference it within the then statement. I’ve tested the query in an earlier BaseX version (10.6), and it produces the expected result (without referencing the Boolean variable again).

 

Thanks in advance,

Tim

 

 

-- 
Tim A. Thompson (he, him)
Librarian for Applied Metadata Research
Yale University Library
www.linkedin.com/in/timathompson