BaseX-Talk March 2025

basex-talk@mailman.uni-konstanz.de

17 participants
14 discussions

BaseX 11.8: Lightning fast maps, new XQuery 4 features
by Christian Grün 30 Apr '25

30 Apr '25

We are delighted to announce BaseX 11.8, one more important step to the next major version. Here are the most significant changes: - [MOD] Lightning fast construction of ordered maps of all types - [MOD] fn:distinct-values, fn:duplicate-values: faster comparisons - [MOD] Faster map comparison (ordered and unordered) - [ADD] New function util:values-except - [ADD] XQuery 4.0 functionality (functions, %method annotation) - [MOD] XQuery fold functions: more early exits - [MOD] XQuery, fn:parse-xml: options added - [MOD] prof:variables: Better capture of in-scope variables - [FIX] Stricter permission checks when calling built-in functions For a preview of the upcoming 12 features, please visit the following page… https://docs.basex.org/12 …and have a look at our homepage to download the latest version: https://basex.org Have fun, Your BaseX Team

2 3

11.8: Store always clearing on restart
by Zimmel, Daniel 26 Mar '25

26 Mar '25

Hi, is this a bug? The store is always clearing on restart. In contrast, the documentation says: "The store will still be available if BaseX is restarted until it is cleared." https://docs.basex.org/main/Store_Functions It works as documented in 11.6, but not in 11.7 and 11.8. Steps to reproduce via GUI: 11.6: Start GUI XQuery: store:put('TEST','TEST') Close GUI Start GUI XQuery: store:get('TEST') Result: 'TEST' 11.7/8: Start GUI XQuery: store:put('TEST','TEST') Close GUI Start GUI XQuery: store:get('TEST') Result is empty The changelog for 11.7 says (not related?): [MOD] Store functions: only read if contents have changed (https://basex.org/2025/01/31/basex-11.7/) Cheers, Daniel

2 3

Re: document-uri() and base-uri() functions in BaseX 11.8
by ykhabins＠bellsouth.net 25 Mar '25

25 Mar '25

Hi Gunther, I tested the latest build, BaseX 11.9 beta c55e0e8 Everything is back to normal. The document-uri() and base-uri() functions working as expected. Thanks a lot for such quick turn-around with the fix. Regards, Yitzhak Khabinsky

1 0

Re: document-uri() and base-uri() functions in BaseX 11.8
by ykhabins＠bellsouth.net 25 Mar '25

25 Mar '25

Hi Gunter, I tested the latest build, BaseX 11.9 beta c55e0e8 Everything is back to normal. The document-uri() and base-uri() functions working as expected. Thanks a lot for such quick turn-around with the fix. Regards, Yitzhak Khabinsky

1 0

document-uri() and base-uri() functions in BaseX 11.8
by ykhabins＠bellsouth.net 25 Mar '25

25 Mar '25

Hello, Congrats on the BaseX 11.8 release. Was there a change in BaseX 11.8 to the document-uri() and base-uri() functions behavior? It seems that they are striping out a file name at the end of the fully qualified file path on the file system! Please find below a repro of it. BaseX 11.7 ========== declare variable $base_dir as xs:string := 'e:\Temp\Identity Transformation88\'; for $x at $i in collection($base_dir) let $file := tokenize(document-uri($x), '/')[last()] return (document-uri($x), $file) Emits the following as expected: file:///E:/Temp/Identity%20Transformation88/Input.xml Input.xml file:///E:/Temp/Identity%20Transformation88/Output.xml Output.xml BaseX 11.8 ========== The same XQuery emits the following: file:///E:/Temp/Identity%20Transformation88/ file:///E:/Temp/Identity%20Transformation88/ Regards, Yitzhak Khabinsky

2 2

Pretty printing of results in BaseX GUI.
by Buddy Kresge 25 Mar '25

25 Mar '25

In BaseX GUI (Version 10.5), I cannot get the pretty printing to work. I have the below option configured in .basexgui but it appears to have no impact, as the XML that is output in the Results area is NOT pretty printed. Can you advise on how to best get the pretty printing of the XML to happen in BaseX GUI? # Local Options SERIALIZER = indent=yes Buddy Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

2 4

Great work! Thank you basex folks
by Liedtke, Alexander 23 Mar '25

23 Mar '25

Thanks for the great work and the new version update! I think everybody using basex should consider using the (pretty good hidden) donate button at the bottom of the basex.org homepage, to at least spend the devs a good weekend with coffee or beer… 😉

2 2

csv:parse header option not working in version 11.7
by Lizzi, Vincent 19 Mar '25

19 Mar '25

Hi BaseX team, Has the "header" option on csv:parse changed between BaseX version 11.6 and 11.7? Here is an example to illustrate what looks like a problem or change. Given a tab separated text file such as this: aaaa bbbb cccc a1 b1 c1 a2 b2 c2 This query uses the "header": "yes" option on csv:parse which should map column names to element names. "tsv-test.tsv" => file:resolve-path() => file:read-text() => csv:parse(map{'separator': 'tab', 'header': 'yes'}) BaseX version 11.6 produces the expected parse: <csv> <record> <aaaa>a1</aaaa> <bbbb>b1</bbbb> <cccc>c1</cccc> </record> <record> <aaaa>a2</aaaa> <bbbb>b2</bbbb> <cccc>c2</cccc> </record> </csv> BaseX version 11.7 seems to be ignoring the header option and produces this output: <csv> <record> <entry>aaaa</entry> <entry>bbbb</entry> <entry>cccc</entry> </record> <record> <entry>a1</entry> <entry>b1</entry> <entry>c1</entry> </record> <record> <entry>a2</entry> <entry>b2</entry> <entry>c2</entry> </record> </csv> If this is an expected change, is there any equivalent to the option "header": "yes" ? Best regards, Vincent ______________________________________________ Vincent M. Lizzi Head of Information Standards | Taylor & Francis Group E-Mail: vincent.lizzi(a)taylorandfrancis.com<mailto:vincent.lizzi@taylorandfrancis.com> Web: www.tandfonline.com<http://www.tandfonline.com/> Time zone: US Eastern Taylor & Francis is a trading name of Informa UK Limited, registered in England under no. 1072954 "Everything should be made as simple as possible, but not simpler." Information Classification: General

3 4

HTTP server performance seems very slow...
by Peter Villadsen 15 Mar '25

15 Mar '25

All, I have been using BaseX for a while, connecting to the TCP endpoint. I know the performance I typically get, and it is impressive! However, now I wanted to use the HTTP endpoint, and it seems the performance is at least 2 orders of magnitude worse! Here is the query that I am POSTing to http://localhost:8984/rest/RainFnd_6.0.10.0 <query xmlns=http://basex.org/rest> <text>/Class[@Package='ApplicationPlatform']/@Name</text> </query> This simple query will generate around 1500 results from the 13GB database (RainFnd_6.0.10.0<http://localhost:8984/rest/RainFnd_6.0.10.0>). It takes just over 7 seconds to do this. If I do this in the BaseX GUI that is self contained, it takes around 20ms. However, it seems that the time spent executing the query against the database is negligible. Please consider this query: <query xmlns=http://basex.org/rest> <text>1 + 2</text> </query> In which there there is obviously no database access. It takes almost the same amount of time as the query that accesses the database. 7 seconds to calculate 1 + 2 is too long. If I post the 1 + 2 query to the endpoint without specifying the database on the URL: http://localhost:8984/rest it takes around 7 milliseconds, close to what I expected, certainly within expectations for the time spent sending the query over the wire and serializing etc. This leads me to believe that a lot of the time (>7 seconds) may be spent opening the database each time a POST is done? Is there a way to tweak the HTTP server to "remember" the connection with the current database for a little while? This may be against the REST principles, of course. The database is guaranteed to be read-only in my case. The problem is that this makes the HTTP server inappropriate for interactive applications. I can still use the TCP server, where I get the results I need, but using the HTTP would be simpler, and have less overhead in terms of code needed to communicate with the server. Please let me know if there is a way to accomplish acceptable performance with the HTTP server. Best Regards Peter Villadsen Principal Technical Program Manager Microsoft Business Applications Group

3 7

Protecting against XML vulnerabilities
by Nico Verwer (Rakensi) 14 Mar '25

14 Mar '25

I am trying to protect my BaseX application from XML vulnerabilities, like the ones described in [https://gist.github.com/mgeeky/4f726d3b374f0a34267d4f19c9004870] and [https://learn.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-d…]. My application runs as `basexhttp` inside a docker container, and I set the options in web.xml: <context-param> <param-name>org.basex.dtd</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>org.basex.xinclude</param-name> <param-value>false</param-value> </context-param> I have not found other options, for example to let the parser limit expansion of internal entities. Is there a way to set parser properties like `jdk.xml.entityExpansionLimit` in BaseX?

4 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk March 2025