Re: [basex-talk] BaseX 9.3: The Winter Edition; {position()>1] vs. [./position()>1

you are absolutely right - the old the old basex version (9,2,4) considered both statements as equal. This means - the issue was in 9.2.4 and is fixed in 9.3 ... sometimes existing code makes existing bugs accessible as features thanks in advance alex Am 02.12.2019 um 21:07 schrieb Christian

Re: [basex-talk] BaseX 9.3: The Winter Edition; {position()>1] vs. [./position()>1

Hi Alex, Could you share a little self-contained example with us that demonstrates the wrong behavior, and name the versions of BaseX you tested? The two following expressions are equivalent: //row[position() > 1] /descendant-or-self::node()/child::row[position() > 1] They are not

[basex-talk] BaseX 9.3: The Winter Edition; {position()>1] vs. [./position()>1

the results of equivalent semantics: e.g. //row[position()>1] is no more equal to in latest 9.3 release to //row[./position()>1] the later results in not correct result. Alex

Re: [basex-talk] BaseX 9.3: The Winter Edition

Thank you all so much! The list of improvements is really impressive! Great job as usual. M. On 29/11/19 17:14, Christian Grün wrote: Hello to our loyal readers of our list, We are glad to announce version 9.3 of BaseX, our XML framework, database system and XQuery 3.1 processor:

Re: [basex-talk] BaseX 9.3: The Winter Edition

Christian, and the BaseX Team - Congratulations on the new release! Thank you for all of your time and efforts. Best, Bridger On Fri, Nov 29, 2019 at 11:14 AM Christian Grün wrote: > Hello to our loyal readers of our list, > > We are glad to announce version 9.3 of BaseX, our XML framework, >

[basex-talk] BaseX 9.3: The Winter Edition

Hello to our loyal readers of our list, We are glad to announce version 9.3 of BaseX, our XML framework, database system and XQuery 3.1 processor: http://basex.org/ The focus has been put on in-depth optimizations of complex XQuery code and faster processing of RESTXQ web applications: