Hello all,
after switching to 7.8.2 we started to get this error:
XUST001 Updating function items are not yet supported
when passing an updating function as a value. This used to work neatly from 7.6 at least onwards. I must admit that I'm pretty surpirsed and I'd like to ask where ni the docs I could get more info on that. Thanks. Regards, Marco.
Hi Marco,
XUST001 Updating function items are not yet supported
when passing an updating function as a value. This used to work neatly from 7.6 at least onwards. I must admit that I'm pretty surpirsed and I'd like to ask where ni the docs I could get more info on that.
the behavior in 7.6 was not clean, which is why it was removed in more recent versions. However, the latest XQUF draft (not public yet) now provides an "updating" keyword, which can be used to invoke updating functions
UpdatingFunctionCall ::= "updating" PrimaryExpr "(" (ExprSingle ("," ExprSingle)*)? ")"
Issue 939 will be closed as soon as we have implemented this in BaseX [1]. As an alternative, if you set MIXUPDATES=true in BaseX 8.0, you won't encounter any restrictions regarding the invocation of updating and non-updating functions.
Christian
Et voilà...
https://github.com/BaseXdb/basex/issues/939 http://files.basex.org/releases/latest/
Your feedback is welcome, Christian
On Tue, Apr 22, 2014 at 3:31 PM, Christian Grün christian.gruen@gmail.com wrote:
Hi Marco,
XUST001 Updating function items are not yet supported
when passing an updating function as a value. This used to work neatly from 7.6 at least onwards. I must admit that I'm pretty surpirsed and I'd like to ask where ni the docs I could get more info on that.
the behavior in 7.6 was not clean, which is why it was removed in more recent versions. However, the latest XQUF draft (not public yet) now provides an "updating" keyword, which can be used to invoke updating functions
UpdatingFunctionCall ::= "updating" PrimaryExpr "(" (ExprSingle ("," ExprSingle)*)? ")"
Issue 939 will be closed as soon as we have implemented this in BaseX [1]. As an alternative, if you set MIXUPDATES=true in BaseX 8.0, you won't encounter any restrictions regarding the invocation of updating and non-updating functions.
Christian
acclaim
On 04.05.2014 21:57, Christian Grün wrote:
Et voilà...
https://github.com/BaseXdb/basex/issues/939 http://files.basex.org/releases/latest/
Your feedback is welcome, Christian
Nice Christian. We'll try it asap. M.
On 04/05/2014 21:57, Christian Grün wrote:
Et voilà...
https://github.com/BaseXdb/basex/issues/939 http://files.basex.org/releases/latest/
Your feedback is welcome, Christian
On Tue, Apr 22, 2014 at 3:31 PM, Christian Grün christian.gruen@gmail.com wrote:
Hi Marco,
XUST001 Updating function items are not yet supported
when passing an updating function as a value. This used to work neatly from 7.6 at least onwards. I must admit that I'm pretty surpirsed and I'd like to ask where ni the docs I could get more info on that.
the behavior in 7.6 was not clean, which is why it was removed in more recent versions. However, the latest XQUF draft (not public yet) now provides an "updating" keyword, which can be used to invoke updating functions
UpdatingFunctionCall ::= "updating" PrimaryExpr "(" (ExprSingle ("," ExprSingle)*)? ")"
Issue 939 will be closed as soon as we have implemented this in BaseX [1]. As an alternative, if you set MIXUPDATES=true in BaseX 8.0, you won't encounter any restrictions regarding the invocation of updating and non-updating functions.
Christian
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Imsieke, Gerrit, le-tex -
Marco Lettere