Dear all, BaseX 8.6 is out! The new version of our XML database system and XQuery 3.1 processor includes countless improvements and optimizations. Many of them have been triggered by your valuable feedback, many others are the result of BaseX used in productive and commercial environments. The most prominent new features are: LOCKING - jobs without database access will never be locked - read transactions are now favored (adjustable via FAIRLOCK) RESTXQ - file monitoring was improved (adjustable via PARSERESTXQ) - authentication was reintroduced (no passwords anymore in web.xml) - id session attributes will show up in log data DBA - always accessible, even if job queue is full - pagination of table results INDEXING - path index improved: distinct values storage for numeric types XQUERY - aligned with latest version of XQuery 3.1 - updated functions: map:find, map:merge, fn:sort, array:sort, ... - enhancements in User, Process, Jobs, REST and Database Module CSV DATA - improved import/export compatibility with Excel data Visit http://basex.org to find the latest release, and check out http://docs.basex.org/ to get more information. As always, we are looking forward to your feedback. Enjoy! Christian BaseX Team
Hi Christian - thank you and the rest of the BaseX team! I'm looking forward to enjoying the new version. Best, Bridger On Tue, Jan 24, 2017 at 12:54 PM, Christian Grün <christian.gruen@gmail.com> wrote:
Dear all,
BaseX 8.6 is out! The new version of our XML database system and XQuery 3.1 processor includes countless improvements and optimizations. Many of them have been triggered by your valuable feedback, many others are the result of BaseX used in productive and commercial environments.
The most prominent new features are:
LOCKING - jobs without database access will never be locked - read transactions are now favored (adjustable via FAIRLOCK)
RESTXQ - file monitoring was improved (adjustable via PARSERESTXQ) - authentication was reintroduced (no passwords anymore in web.xml) - id session attributes will show up in log data
DBA - always accessible, even if job queue is full - pagination of table results
INDEXING - path index improved: distinct values storage for numeric types
XQUERY - aligned with latest version of XQuery 3.1 - updated functions: map:find, map:merge, fn:sort, array:sort, ... - enhancements in User, Process, Jobs, REST and Database Module
CSV DATA - improved import/export compatibility with Excel data
Visit http://basex.org to find the latest release, and check out http://docs.basex.org/ to get more information. As always, we are looking forward to your feedback. Enjoy!
Christian BaseX Team
Super! Thanks. Il giorno 24 gen 2017, alle ore 18:54, Christian Grün <christian.gruen@gmail.com> ha scritto: Dear all, BaseX 8.6 is out! The new version of our XML database system and XQuery 3.1 processor includes countless improvements and optimizations. Many of them have been triggered by your valuable feedback, many others are the result of BaseX used in productive and commercial environments. The most prominent new features are: LOCKING - jobs without database access will never be locked - read transactions are now favored (adjustable via FAIRLOCK) RESTXQ - file monitoring was improved (adjustable via PARSERESTXQ) - authentication was reintroduced (no passwords anymore in web.xml) - id session attributes will show up in log data DBA - always accessible, even if job queue is full - pagination of table results INDEXING - path index improved: distinct values storage for numeric types XQUERY - aligned with latest version of XQuery 3.1 - updated functions: map:find, map:merge, fn:sort, array:sort, ... - enhancements in User, Process, Jobs, REST and Database Module CSV DATA - improved import/export compatibility with Excel data Visit http://basex.org to find the latest release, and check out http://docs.basex.org/ to get more information. As always, we are looking forward to your feedback. Enjoy! Christian BaseX Team
Looks good. PARSERESTXQ makes a big difference for me. The spec change for map:merge [1] used with the idiom map:merge (($defaults,$opts)) required a few changes :-) A question about jobs:list-details[2] I had expected the attribute duration: evaluation time (for running and cached jobs) to be frozen once the job is cached. This is seems not to be the case. Is this intended behaviour? jobs:list-details("job369") <job id="job369" type="ScheduledXQuery" state="cached" user="admin" reads="(none)" writes="(none)" duration="PT28.927S">(1 to 500000000)[0=.]=>empty()</job> jobs:list-details("job369") <job id="job369" type="ScheduledXQuery" state="cached" user="admin" reads="(none)" writes="(none)" duration="PT39.791S">(1 to 500000000)[0=.]=>empty()</job> /Andy [1] http://docs.basex.org/wiki/Map_Module#map:merge [2] http://docs.basex.org/wiki/Jobs_Module#jobs:list-details On 25 January 2017 at 06:15, meumapple <meumapple@gmail.com> wrote:
Super! Thanks.
Il giorno 24 gen 2017, alle ore 18:54, Christian Grün < christian.gruen@gmail.com> ha scritto:
Dear all,
BaseX 8.6 is out! The new version of our XML database system and XQuery 3.1 processor includes countless improvements and optimizations. Many of them have been triggered by your valuable feedback, many others are the result of BaseX used in productive and commercial environments.
The most prominent new features are:
LOCKING - jobs without database access will never be locked - read transactions are now favored (adjustable via FAIRLOCK)
RESTXQ - file monitoring was improved (adjustable via PARSERESTXQ) - authentication was reintroduced (no passwords anymore in web.xml) - id session attributes will show up in log data
DBA - always accessible, even if job queue is full - pagination of table results
INDEXING - path index improved: distinct values storage for numeric types
XQUERY - aligned with latest version of XQuery 3.1 - updated functions: map:find, map:merge, fn:sort, array:sort, ... - enhancements in User, Process, Jobs, REST and Database Module
CSV DATA - improved import/export compatibility with Excel data
Visit http://basex.org to find the latest release, and check out http://docs.basex.org/ to get more information. As always, we are looking forward to your feedback. Enjoy!
Christian BaseX Team
Hi Andy,
A question about jobs:list-details[2] I had expected the attribute duration: evaluation time (for running and cached jobs) to be frozen once the job is cached.
So true; now fixed [1]. Thanks, Christian [1] http://files.basex.org/releases/latest/
This is seems not to be the case. Is this intended behaviour?
jobs:list-details("job369")
<job id="job369" type="ScheduledXQuery" state="cached" user="admin" reads="(none)" writes="(none)" duration="PT28.927S">(1 to 500000000)[0=.]=>empty()</job>
jobs:list-details("job369")
<job id="job369" type="ScheduledXQuery" state="cached" user="admin" reads="(none)" writes="(none)" duration="PT39.791S">(1 to 500000000)[0=.]=>empty()</job>
/Andy [1] http://docs.basex.org/wiki/Map_Module#map:merge [2] http://docs.basex.org/wiki/Jobs_Module#jobs:list-details
On 25 January 2017 at 06:15, meumapple <meumapple@gmail.com> wrote:
Super! Thanks.
Il giorno 24 gen 2017, alle ore 18:54, Christian Grün <christian.gruen@gmail.com> ha scritto:
Dear all,
BaseX 8.6 is out! The new version of our XML database system and XQuery 3.1 processor includes countless improvements and optimizations. Many of them have been triggered by your valuable feedback, many others are the result of BaseX used in productive and commercial environments.
The most prominent new features are:
LOCKING - jobs without database access will never be locked - read transactions are now favored (adjustable via FAIRLOCK)
RESTXQ - file monitoring was improved (adjustable via PARSERESTXQ) - authentication was reintroduced (no passwords anymore in web.xml) - id session attributes will show up in log data
DBA - always accessible, even if job queue is full - pagination of table results
INDEXING - path index improved: distinct values storage for numeric types
XQUERY - aligned with latest version of XQuery 3.1 - updated functions: map:find, map:merge, fn:sort, array:sort, ... - enhancements in User, Process, Jobs, REST and Database Module
CSV DATA - improved import/export compatibility with Excel data
Visit http://basex.org to find the latest release, and check out http://docs.basex.org/ to get more information. As always, we are looking forward to your feedback. Enjoy!
Christian BaseX Team
Hi List, thank for 8.6! But, it looks like that commands scripts (bxs) not longer working within GUI. Command line mode is fine. Jan Command: EXECUTE <commands> <xquery>1+2</xquery> </commands> Error: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@mailman.uni-konstanz.de Version: BaseX 8.6 Java: Oracle Corporation, 1.8.0_121 OS: Linux, amd64 Stack Trace: java.lang.NullPointerException at org.basex.query.QueryInfo.toString(QueryInfo.java:110) at org.basex.core.cmd.AQuery.query(AQuery.java:105) at org.basex.core.cmd.XQuery.run(XQuery.java:22) at org.basex.core.Command.run(Command.java:257) at org.basex.core.cmd.Execute.run(Execute.java:54) at org.basex.core.Command.run(Command.java:257) at org.basex.core.Command.execute(Command.java:95) at org.basex.gui.GUI.exec(GUI.java:471) at org.basex.gui.GUI.access$300(GUI.java:44) at org.basex.gui.GUI$6.run(GUI.java:413) Compiling: - pre-evaluating (1 + 2) Optimized Query: 3 Query: 1+2 Query plan: <QueryPlan compiled="true"> <Int value="3" type="xs:integer"/> </QueryPlan>
Thanks for the info, Jan. This seems to be a bug related to the Info View. I will fix this tomorrow. Until then, please run your command script with a closed Info View panel. On Thu, Jan 26, 2017 at 4:55 PM, Jan Dölle <basex-list@id1.de> wrote:
Hi List,
thank for 8.6!
But, it looks like that commands scripts (bxs) not longer working within GUI. Command line mode is fine.
Jan
Command: EXECUTE <commands> <xquery>1+2</xquery> </commands> Error: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@mailman.uni-konstanz.de Version: BaseX 8.6 Java: Oracle Corporation, 1.8.0_121 OS: Linux, amd64 Stack Trace: java.lang.NullPointerException at org.basex.query.QueryInfo.toString(QueryInfo.java:110) at org.basex.core.cmd.AQuery.query(AQuery.java:105) at org.basex.core.cmd.XQuery.run(XQuery.java:22) at org.basex.core.Command.run(Command.java:257) at org.basex.core.cmd.Execute.run(Execute.java:54) at org.basex.core.Command.run(Command.java:257) at org.basex.core.Command.execute(Command.java:95) at org.basex.gui.GUI.exec(GUI.java:471) at org.basex.gui.GUI.access$300(GUI.java:44) at org.basex.gui.GUI$6.run(GUI.java:413) Compiling: - pre-evaluating (1 + 2) Optimized Query: 3 Query: 1+2 Query plan: <QueryPlan compiled="true"> <Int value="3" type="xs:integer"/> </QueryPlan>
Thanks again for your mail. The bug has been fixed [1]. Cheers, Christian [1] http://files.basex.org/releases/latest/ On Thu, Jan 26, 2017 at 4:55 PM, Jan Dölle <basex-list@id1.de> wrote:
Hi List,
thank for 8.6!
But, it looks like that commands scripts (bxs) not longer working within GUI. Command line mode is fine.
Jan
Command: EXECUTE <commands> <xquery>1+2</xquery> </commands> Error: Improper use? Potential bug? Your feedback is welcome: Contact: basex-talk@mailman.uni-konstanz.de Version: BaseX 8.6 Java: Oracle Corporation, 1.8.0_121 OS: Linux, amd64 Stack Trace: java.lang.NullPointerException at org.basex.query.QueryInfo.toString(QueryInfo.java:110) at org.basex.core.cmd.AQuery.query(AQuery.java:105) at org.basex.core.cmd.XQuery.run(XQuery.java:22) at org.basex.core.Command.run(Command.java:257) at org.basex.core.cmd.Execute.run(Execute.java:54) at org.basex.core.Command.run(Command.java:257) at org.basex.core.Command.execute(Command.java:95) at org.basex.gui.GUI.exec(GUI.java:471) at org.basex.gui.GUI.access$300(GUI.java:44) at org.basex.gui.GUI$6.run(GUI.java:413) Compiling: - pre-evaluating (1 + 2) Optimized Query: 3 Query: 1+2 Query plan: <QueryPlan compiled="true"> <Int value="3" type="xs:integer"/> </QueryPlan>
participants (5)
-
Andy Bunce -
Bridger Dyson-Smith -
Christian Grün -
Jan Dölle -
meumapple