Re: [basex-talk] Use of function-lookup in REST-XQ environment

Hi Mauro, Mi dispiace di averti fatto aspettare. Your test case was very helpful for reproducing the issue. The problem was caused by the combination of mixupdates and function-lookup. I hope that the issue is resolved with the latest stable snapshot [1] (it’s time to give it a TLA… maybe LSS?).

Re: [basex-talk] Use of function-lookup in REST-XQ environment

Dear Christian, About this problem we discover another issue that is causing us some troubles. In the same scenario of calling RESTXQ updating functions discovered dynamically in a basex with MIXUPDATES turned on: if a reading function is called on the same DB while an updating function is

Re: [basex-talk] Use of function-lookup in REST-XQ environment

Dear Christian, Thank you so much, it also worked very well in version 9.3.1 that is the one we are using at the moment. We plan to move to the next stable release when it will be available. Thanks also for your words; all the best to all: to Italy and also to people all over the world.

Re: [basex-talk] Use of function-lookup in REST-XQ environment

Dear Mauro, The combination of higher-order functions and MIXUPDATE led to a wrong assignment of static properties of your updating expression. I have made the compilation step more rigid: If a dynamic function call is found, and if mixing updates is enabled, the function will now always be

[basex-talk] Use of function-lookup in REST-XQ environment

Hi all,In order to have a "dynamic backend” implementation to REST-XQ invocations we used the fn:function-lookup() function but we are experiencing a strange behavior if the target looked-up function is an updating function that for example adds a resource to a database.Putting the provided files