September 2023 - 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

use-character-maps vs parameter-document with db:export()
by Zimmel, Daniel 09 Oct '23

09 Oct '23

Hi, when using db:export, the serialization parameter use-character-maps works just fine. But can someone explain why it is not possible to use parameter-document? At least, it does not work here with 10.3. As in: db:export($dbname,$path, map{ 'indent':'no', 'omit-xml-declaration':'no', 'parameter-document':'map.xml' }) OK I can see that there is no parameter-document option in the table I can find here defined for fn:serialize(): https://www.w3.org/TR/xpath-functions-31/#func-serialize When not using db:export(), all is well as described: https://docs.basex.org/wiki/Serialization#Character_mappings So in short, I think the answer is the spec. Is it? Have a nice weekend, Daniel

2 3

XSLT in BaseX - no node parameters
by Hans-Juergen Rennau 25 Sep '23

25 Sep '23

Dear BaseX folks, the documentation of the XSLT module says: "Variables can be bound to a stylesheet via $arguments (only strings are supported when using XSLT 3.0 and Saxon). " That is a pity! Are there plans to remove this limitation? Kind regards,Hans-Jürgen

2 3

Element construction - namespace error - bug?
by Hans-Juergen Rennau 25 Sep '23

25 Sep '23

Dear BaseX folks, constructing elements, I encounter a problem with namespaces which I do not understand. Is it a bug or do I overlook something? To reproduce the problem you need to create an XML file "doc.xml" with this content: <doc xmlns="http://basex.org/simply/the/best"> <foo bar="1"> <peng/> </foo></doc> And here's the query: declare namespace f="http://basex.org/does/its/thing"; declare function f:pretty($n as node()) as node()? { typeswitch($n) case document-node() return document {$n/node() ! f:pretty(.)} case element() return element {node-name($n)} { in-scope-prefixes($n) ! namespace {.} {namespace-uri-for-prefix(., $n)}, $n/@* ! f:pretty(.), $n/node() ! f:pretty(.) } default return $n}; let $doc := doc('doc.xml')return f:pretty($doc) What I get is this error: Stopped at C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 8/33:[XQDY0102] Duplicate declaration of namespace 'http://basex.org/simply/the/best'. Stack Trace:- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 11/33- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 11/33- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 6/63- C:/projects/tableman/prototype/thieme-showcase/xq/demo-namespace-problem.xq, 17/16 Strangely enough, you do not get the error if you copy the contents of doc.xml into the query: let $doc := <doc .../>return f:pretty($doc) You also do not get the error if you remove the @bar attribute in the document. Kind regards,Hans-Jürgen

2 3

Re: [basex-talk] Set Strip Whitespace Mode
by Christian Grün 15 Sep '23

15 Sep '23

Hi Hans-Jürgen, > question: what is the recommended way of ensuring that an application calling BaseX via command-line (basex ...) uses a certain strip whitespace mode (true or false), if the application is deployed on servers with different BaseX versions? Option -w cannot naively be used, as it toggles the strip whitespace mode, so the effect depends on the version. Sounds challenging. You can set the STRIPWS option to an explicit value… basex -c"SET STRIPWS false" query.xq ... …but this will fail as the comparable BaseX 9 option was called CHOP. You could use XQuery to retrieve the version number… data(db:system()//version) …or to check if a specific option is supported: try { prof:void(db:option('chop')), '!' } catch * { '?' } In general, I would recommend updating to the latest version whenever possible… Hope this helps, Christian

1 0

Set strip whitespace mode
by Hans-Juergen Rennau 15 Sep '23

15 Sep '23

Dear BaseX folks, question: what is the recommended way of ensuring that an application calling BaseX via command-line (basex ...) uses a certain strip whitespace mode (true or false), if the application is deployed on servers with different BaseX versions? Option -w cannot naively be used, as it toggles the strip whitespace mode, so the effect depends on the version. I have not found out how to determine the version of BaseX reliably, using XQuery or a command. So how can a script decide whether or not to use -w? Thank you for help. Kind regards,Hans-Jürgen

1 0

Variable declaration of variable containing a recursive function triggers an error! (golden oldy)
by Rob Stapper 12 Sep '23

12 Sep '23

Hi Christian, I’ve addressed this issue already in feb 2022 and nov 2020. Since I think it is a bug I am coming back on it again. Hopefully with a better formulated argument this time. There is a easy workaround but if code is generated, as in my case, having to change the code manually each time after generation is getting pretty tedious. (and I very much like my code to be consistent) So, why is it that a function-declaration of a function that is recursive doesn’t trigger an self-depending-error and a variable-declaration that has such a function assigned to, does? In the first situation preventing an endless loop is, obviously and rightly so, treated as a programmers responsibility. However in the second situation this responsibility is taken away from the programmer by not even allowing the situation. This is not consistent. Sure, the compiler should and does detect cyclic variable-assignments but that is actually not the case here. Assigning a function to a variable is per definition a non-cyclic assignment. Possible recursiveness in this case should be treated the same as with a function-declaration, that is, as a programmers responsibility. I hope the above makes some sense. Is it worth an effort to address this issue? It would probably make the compiler code even less complex. Cheers, Rob Stapper Sent from Mail for Windows -- This email has been checked for viruses by Avast antivirus software. www.avast.com

2 1

Docker
by Diego Alcorta 05 Sep '23

05 Sep '23

I see that docker images have not been updated in over 2 years. I was wondering what the best way to deploy basex in kubernetes is. -- Diego Alcorta dalcorta(a)gmail.com ----------------------------------------------------- "If patience is a virtue, and ignorance is bliss, you can have a pretty good life if you're ignorant and willing to wait" -----------------------------------------------------

2 1