February 2024 - BaseX-Talk - mailman.uni-konstanz.de

BaseX 9.6: The Summer Edition
by Christian Grün 28 Nov '24

28 Nov '24

Dear all, We provide you with a new and fresh version of BaseX, our open source XML framework, database system and XQuery 3.1 processor: https://basex.org/ Apart from our main focus (query rewritings and optimizations), we have added the following enhancements: XQUERY: MODULES, FEATURES - Archive Module, archive:write: stream large archives to file - SQL Module: support for more SQL types - Full-Text Module, ft:thesaurus: perform Thesaurus queries - Fulltext, fuzzy search: specify Levenshtein limit - UNROLLLIMIT option: control limit for unrolling loops XQUERY: JAVA BINDINGS - Java objects of unknown type are wrapped into function items - results of constructor calls are returned as function items - the standard package "java.lang." has become optional - array arguments can be specified with the middle dot notation - conversion can be controlled with the WRAPJAVA option - better support for XQuery arrays and maps WEB APPLICATIONS - RESTXQ: Server-Timing HTTP headers are attached to the response For a more comprehensive list of added and updated features, look into our documentation (docs.basex.org) and check out the GitHub issues (github.com/BaseXdb/basex/issues) Have fun, Your BaseX Team

11 43

recursively used variables
by Rob Stapper 12 Aug '24

12 Aug '24

Hi, The code[1] below and send as attachment generates a error message: “Static variable depends on itself: $Q{http://www.w3.org/2005/xquery-local-functions}test”. I use these variables to refer to my private functions in my modules so I can easyly refer to them in a inheritance situation. It’s not a big problem for me but I was wondering if the error-triggering is justified or that it should work. [1]=========================================== declare variable $local:test := local:test#1 ; declare %private function local:test( $i) { if ( $i > 0) then $local:test( $i - 1) } ; $local:test( 10) =========================================== Kind regards, Rob Stapper Sent from Mail for Windows 10 -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

4 7

xslt:transform-report result
by Andy Bunce 11 Mar '24

11 Mar '24

Hi, Using BaseX 9.7.1 and saxon9he-9.9.1.jar The documentation suggests the ?result from xslt:transform-report should be *a* document-node where possible [1] This seems not quite to be the case when there are processing instructions or comments at the top level. In these cases a sequence of document-nodes is returned. /Andy [1] https://docs.basex.org/wiki/XSLT_Module#xslt:transform-report let $xslt:=<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"> <xsl:mode on-no-match="shallow-copy"/> </xsl:stylesheet> let $xml:=document{ <?something type="compact"?>, <foo/>} return xslt:transform-report($xml,$xslt) Returns map { "messages": (), "result": (<?something type="compact"?>, <foo/>) }

3 7

Troubles with ft:mark
by Jack Steyn 07 Mar '24

07 Mar '24

Hi BaseXers, Consider the following query run on a database 'factbook' containing factbook.xml with full-text indexing: declare function local:search( $database as xs:string, $query as xs:string ) { let $country-search := ft:search($database, $query)/ancestor::country let $city-search := ft:search($database, $query)/ancestor::city/ancestor::country let $other-search := ft:search($database, $query)/parent::*[name() = ('ethnicgroups', 'languages')]/ancestor::country let $country-mark := $country-search[.//name[text() contains text { $query }]] => ft:mark() let $city-mark := $city-search[.//city[text() contains text { $query }]] => ft:mark() let $other-mark := $other-search[.//*[name() = ('ethnicgroups', 'languages')][text() contains text { $query }]] => ft:mark() return ( $country-mark, $city-mark, $other-mark ) }; local:search('factbook', 'German') The first result of this query is the entry for Austria. I would expect both of the instances of the word 'German' in that entry to be surrounded by <mark> tags. However only the first instance is. Some changes that produce the correct result for the Austria entry: - replacing $database with 'factbook' in the definition of $other-search, or - deleting either $country-mark or $city-mark in the sequence returned. If you make either of the above changes, but additionally change the predicate [text() contains text { $query }] to [ft:contains(text(), $query)], the incorrect result returns. Any idea what might be causing this? I'm running BaseX 10.7. Cheers, Jack

2 5

Optimize database never returns, leaves database in "opened by another process" state
by Eliot Kimber 04 Mar '24

04 Mar '24

Using Basex 10.7 on Linux. I’m running a sequence of jobs to update and optimize a set of databases following loading a number of documents created dynamically (as opposed to being read from disk). I’m seeing a new behavior, which is that the optimization step never completes but also doesn’t show any error in the log. The database shows no items and is in the locked by another process state if I try to drop it. This behavior seems to be consistently repeatable with my current code base (I’m working on some code updates, so it’s possible I’ve introduced something that would cause this behavior but I haven’t changed the code that leads up to the failing optimize). The server has plenty of disk space, etc. Optimization code is: try { if (db:exists($database)) then ( util:logToConsole('dbadmin:optimizeDatabase', ``[Optimizing database `{$database}`]``), db:optimize($database, true(), $dbadmin:dbOptimizeOptions) ) else util:logToConsole('dbadmin:optimizeDatabase', ``[Database '`{$database}`' does not exist. Nothing to optimize.]``) } catch * { util:logToConsole( 'dbadmin:optimizeDatabase', ``[Exception optimizing database '`{$database}`': `{$err:code}` - `{$err:description}`]``, 'error') } And the optimization options are: declare variable $dbadmin:dbOptimizeOptions as map(*) := (: Turn on all the indexes :) map { 'attrindex' : true(), 'tokenindex' : true(), 'textindex' : true(), 'ftindex' : true() }; This code has been working fine for a long time and I’ve been running 10.7 for a least a couple of months, so I’m wondering: A) Would would cause this behavior? B) How can I diagnose it short of debugging the Java code (which I can do but it’s non-trivial for me to set up). Thanks, Eliot _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow>

3 10

Re: [basex-talk] Item Separator
by Leo Studer 29 Feb '24

29 Feb '24

Dear Martin Thank you for investigating. > The "text1, , text2" I only see if oXygen shows the result as a sequence in its result viewer; I would suggest to ask the oXygen support why you get that result for that case, it seems like some quirk in their result viewer (it shows two xs:string items but for reasons I can't investigate serializes the two items for the result viewer as "text1, , text2"). > This is incredible news. I will get to Oxygen about that. Really troubling … Blessings, Leo

1 0

Odd "Access denied" messages in the log
by Eliot Kimber 28 Feb '24

28 Feb '24

I have an application (our Mirabel system) running on a server inside our firewall (so not visible to the open Internet). I’ve recently started seeing messages like this in the log: Access denied: ��. Access denied: PRI * HTTP/2.0 SM . Where the value reported can be quite varied, but is often unrenderable characters or other stuff. (In this case the characters are all \uFFFD). The log messages all report the same IP address. This server does not use named users, so there’s no authentication required to access it. The IP address is not one of my own servers, so I don’t think it’s something generated by my own code. Any idea what this might be? It’s started relatively recently, which makes me think it might be some sort of penetration test. Cheers, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow>

2 1

Item Separator
by Leo Studer 27 Feb '24

27 Feb '24

Hello I am serialising the following expressions on oxygen/saxonEE12.3 as text (item-separator=“”) and wonder why the differente outputs let $xml:=<xml><element>text1</element><element>text2</element></xml> return $xml/element/text() gives text1text2 And let $xml:=<xml><element>text1</element><element>text2</element></xml> return $xml/element/string() text1 text2 When I set the item-separator =“, “ then I get text1, text2 Or text1, , text2 Any explanations??? Thanks, Leo

3 3

file:write, formatting, and maps in select attributes
by Graydon Saunders 24 Feb '24

24 Feb '24

Hello -- I'm trying to regularize the formatting of some XSLT files by loading them (via doc()) and writing them back out via file:write() I know about the *indent* and *indent-attributes* serialization parameters, and mostly they're doing what I want. What I'd like is to preserve a one-line-per-entry format for a map in a select attribute. For example, I'd like to keep <xsl:variable as="map(xs:integer,xs:string)" name="hexNum" select=" map { 1: '0', 2: '1', 3: '2', 4: '3', 5: '4', 6: '5', 7: '6', 8: '7', 9: '8', 10: '9', 11: 'a', 12: 'b', 13: 'c', 14: 'd', 15: 'e', 16: 'f' }" static="yes" /> instead of <xsl:variable as="map(xs:integer,xs:string)" name="hexNum" select=" map { 1: '0', 2: '1', 3: '2', 4: '3', 5: '4', 6: '5', 7: '6', 8: '7', 9: '8', 10: '9', 11: 'a', 12: 'b', 13: 'c', 14: 'd', 15: 'e', 16: 'f' }" static="yes"/> I don't think there's a way to do this with the serialization parameters, but is there a way to do this? Thanks! Graydon -- Graydon Saunders | graydonish(a)fastmail.com Þæs oferéode, ðisses swá mæg. -- Deor ("That passed, so may this.")

3 3

basex failed to cast large numbers as xs:integer
by mx z 22 Feb '24

22 Feb '24

Hi, I found a bug in basex. Version: 1ce0618 (2024.02.22) Java: openjdk 17.0.9 2023-10-17 LTS OpenJDK Runtime Environment Corretto-17.0.9.8.1 (build 17.0.9+8-LTS) OpenJDK 64-Bit Server VM Corretto-17.0.9.8.1 (build 17.0.9+8-LTS, mixed mode, sharing) OS: Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy input.xml: <a xmlns:C="p"> <C:A id="1">1458820431</C:A>1438466813 </a> query.xq: //*[not(. castable as xs:integer)] Reproduce: java -cp basex-core/target/basex-11.0-SNAPSHOT.jar org.basex.BaseX -i input.xml query.xq It printed out <a xmlns:C="p"> <C:A id="1">1458820431</C:A>1438466813 </a> While basex should return empty, as both 1458820431 and 1438466813 are integers. Max Zhang

2 1