Re: [basex-talk] Unexpected unary lookup result

2018-05-11 Thread Giuseppe Celano
Hi Sebastian, In my Basex 9.0.1 and 8.6.7 you get two "true". Best, Giuseppe Universität Leipzig Institute of Computer Science, NLP Augustusplatz 10 04109 Leipzig Deutschland E-mail: cel...@informatik.uni-leipzig.de E-mail: giuseppegacel...@gmail.com Web site 1:

Re: [basex-talk] Unexpected unary lookup result

2018-05-11 Thread Sebastian Zimmer
Hi again, the problem is gone now after a reboot. It seems that the web server was running on another version while the console was running with 9.0.1 Sorry for the inconvenience. Best, Sebastian Am 11.05.2018 um 11:04 schrieb Sebastian Zimmer: Hi Giuseppe, thanks for checking. I

Re: [basex-talk] Unexpected unary lookup result

2018-05-11 Thread Sebastian Zimmer
Sorry to bother you again, but I think there is still something wrong with my code and I can't figure it out. This time I checked it consistently on BaseX 9.0.1 (Windows and Linux, console and web server), results are always the same: xquery version "3.1"; declare namespace array =

Re: [basex-talk] Unexpected unary lookup result

2018-05-11 Thread Sebastian Zimmer
Hi Giuseppe, thanks for checking. I double-checked again. The problem is even weirder now: When using the console, I too get 2x true: $ ./bin/basex "./webapp/array_test.xql" true true When using the web server, I still get this: $ curl localhost:8994/rest?run=array_test.xql false true At

Re: [basex-talk] Unexpected unary lookup result

2018-05-11 Thread Giuseppe Celano
The error is in Basex 9.0.1 but not in 8.6.7. It seems to be caused by the presence of the function within the lambda function. Universität Leipzig Institute of Computer Science, NLP Augustusplatz 10 04109 Leipzig Deutschland E-mail: cel...@informatik.uni-leipzig.de E-mail:

Re: [basex-talk] 9.0.1: High Memory Usage Loading Docs Via GUI

2018-05-11 Thread Eliot Kimber
More experimentation indicates that the issue is the DTDs--if I load the same content without DTD parsing then it loads fine and takes the expected relatively small amount of memory. I think the solution is to turn on Xerces' grammar caching. The only danger there is that different DTDs within