Re: [basex-talk] Optimizer and JSON/XML response

Hi Christian, I'll try to answer your questions inline ... On 16/05/19 19:38, Christian Grün wrote: Hi Marco, We haven’t experienced such a behavior by ourselves, even in very complex applications. Is the faulty behavior reproducible? Only with the exact configuration of our current applciatio

Re: [basex-talk] Optimizer and JSON/XML response

Hi Marco, We haven’t experienced such a behavior by ourselves, even in very complex applications. Is the faulty behavior reproducible? Does it make a difference if you change the value of the PARSERESTXQ option [1]? And is it already the http:send-request call that returns the wrong result, or is

Re: [basex-talk] Optimizer and JSON/XML response

Just to add up ... BaseX version is 9.0.2. Moreover when running from a schedule service job the only way to avoid the issue described is to always first call another RESTXQ and then [1]. Which is somehow what I expect if services are run in their own process/jvm... Despite the subject of the

[basex-talk] Optimizer and JSON/XML response

Hello everyone, we came accross an inconsistency which we are not able to find an explanation for and giving up after having spent on it the whole morning... From a restxq we call an external REST service (InfluxDB) like shown in [1]. This usually works as expected returning a response forged