Hi Marc,
Am 18.03.2015 um 21:08 schrieb Marc:
As I understand the first part of answer, you tell that when there is a user defined function Basex do cache, but after when you analyze the example, you tell that in this cxase there is no cache else there is a f:processNode function in the return.
Do I you don't understand?
well, kind of. When evaluating a call to a user-defined function (that was not inlined during compilation), both the arguments and the result of the call are fully evaluated and cached in memory. This is still the case in Hans-Jürgen's example.
As I understand his question however, he is mostly concerned about the (potentially very big) sequence of nodes that the `for` loop iterates over. I just pointed out that that sequence will not normally be cached by BaseX.
Hope that clears it up, chears, Leo