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

BaseX 10.7: The Summer Edition
by Christian Grün 09 Aug '23

09 Aug '23

Dear all, We’re pleased to announce version 10.7 of BaseX, of our XML framework: https://basex.org. The new release is a big step forward towards BaseX 11: • We have added numerous new operators, functions and features of XQuery 4. • The GUI editor and result view now provide full support for Unicode characters. • Font rendering has been improved (you can tweak it in the Font Dialog) • More BaseX 11 preview features available (see docs.basex.org) • Various bug fixes (web:forward, job:eval, main-memory documents) Have fun, Your BaseX Team

3 3

Re: [basex-talk] Problem with creating new database from GUI
by Christian Grün 08 Aug '23

08 Aug '23

Hi Andreas (cc to the list), Thanks for forwarding the error message, which indicates that removed »Text Parser« may have caused the problem [1]. Good to know it works again. Best, Christian [1] https://docs.basex.org/wiki/Parsers#Changelog On Mon, Aug 7, 2023 at 5:57 PM Andreas Hartmann <andreas.hartmann(a)gmx.org> wrote: > Hi Christian, > > > > in fact I installed BaseX from the .exe. I did now try the .jar and .zip > and those work without any problems. Then I did a clean reinstall with the > .exe and this seems to have fixed the problem. This is the first time I had > problems with installing a new version over an existing installation. > > > > For what it’s worth, when starting the jar-file from the .exe before the > reinstall and clicking on the icon I got in the command line: > > > > Exception in thread "AWT-EventQueue-0" > java.lang.ArrayIndexOutOfBoundsException: Index 3 out of bounds for length 3 > > at > org.basex.gui.dialog.DialogParsing.setType(DialogParsing.java:79) > > at org.basex.gui.dialog.DialogImport.action(DialogImport.java:165) > > at org.basex.gui.dialog.DialogNew.action(DialogNew.java:115) > > at org.basex.gui.dialog.DialogNew.<init>(DialogNew.java:105) > > at org.basex.gui.GUIMenuCmd$1.execute(GUIMenuCmd.java:40) > > at > org.basex.gui.layout.BaseXButton.lambda$command$2(BaseXButton.java:115) >

2 2

Problem with creating new database from GUI
by Andreas Hartmann 07 Aug '23

07 Aug '23

Hello, since I updated to 10.7 I can no longer create a new database from the GUI. Neither clicking on the icon nor the shortcut CTRL+N cause the database creation window to open. Using the menu also has no effect. The other icons work normally. Thanks, Andreas

2 1

Re: [basex-talk] BaseX 10.7: The Summer Edition
by Christian Grün 07 Aug '23

07 Aug '23

Hi Yitzhak, The documentation in our wiki will be made available with version 11, but you can already browse through the current drafts of the specifications. Many of the listed features are already working: https://qt4cg.org/specifications/xpath-functions-40/Overview.html#changelog https://qt4cg.org/specifications/xquery-40/xquery-40.html#id-revision-log Hope this helps, Christian On Sun, Aug 6, 2023 at 3:53 AM <ykhabins(a)bellsouth.net> wrote: > Congrats on the new BaseX 10.7 release! > > > > >> “We have added numerous new operators, functions and features of XQuery 4.“ > > How to find that new XQuery 4 functionality in the BaseX wiki? > > Is their a particular keyword for that? > > > > > > > *Regards,Yitzhak Khabinsky* > > >

1 0

Webapp authentication flow – how do sessions work?
by Jack Steyn 03 Aug '23

03 Aug '23

Hi all, I'm trying to develop a single-page application in Vue where users can log in and out and have different levels of access. I've more or less cribbed the relevant authentication and permissions code from the DBA webapp (which is not single-page). When I test the API in a program like Postman or Insomnia, everything works as expected. However in the browser I can login successfully but I can't then access any RESTXQ functions which I haven't marked as public with the %perm:allow and %perm:check functions. The core problem is that I don't really understand how sessions work, but it seems like the session isn't persisting across requests that my Vue webapp is sending. Do I need to add something in my webapp code that is being handled automatically when I use the DBA webapp or my API testing software? Any advice would be greatly appreciated. Kind regards, Jack

1 1

Decoding error
by Graydon Saunders 19 Jul '23

19 Jul '23

Hello -- I have some mainframe files which start off in no-known-encoding. Using Basex 10.6, I'm trying to use the bin module to make some character substitutions so the content of these files can be UTF-8. let $charMap as map(*) := map { 33: 93, (: exclamation point ! to close bracket ] :) 162: 91, (: cent-sign ¢ to open bracket [ :) 124: 33, (: pipe character | to exclamation point ! :) 160: 32, (: non-breaking space to plain space :) 26: 32 (: U+001A SUBSTITUTION CHARACTER at the end of the file; do not want :) } let $fromList as xs:integer+ := map:keys($charMap) let $fileList as xs:string+ := file:children($localPath) for $x in $fileList return (file:read-binary($x) ! bin:to-octets(.) ! (if (. = $fromList) then $charMap(.) else .) ! bin:from-octets(.) ! bin:decode-string(.,'UTF-8')) => string-join('') Four of the five sample files work; one of them returns "Decoding error: xff" If I restrict the process to the problematic file and use return (file:read-binary($x) ! bin:to-octets(.) ! (if (. = $fromList) then $charMap(.) else .)) => distinct-values() => sort() I don't find a 255 value. And I'm pretty sure all the codepoints I do have are simple, less than 255, single octet UTF-8 characters. Any suggestions for what I ought to be looking at? Thanks! Graydon -- Graydon Saunders | graydonish(a)fastmail.com Þæs oferéode, ðisses swá mæg. -- Deor ("That passed, so may this.")

3 3

How to get stack trace from an Query Exception?
by Eliot Kimber 13 Jul '23

13 Jul '23

The docs for Try/Catch in in the XQuery_3.0 page say: · $err:additional: error stack trace However, in my testing, this only returns the place where the error was thrown, not the complete stack trace as is shown e.g., in a web app when an exception is thrown. Is it possible to get the stack trace in XQuery? I didn’t find anything searching on the BaseX-supplied DBA app. Thanks, 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

PHP Client Session Object: infinite loop in read method when bpos is null
by Tamara Marnell 13 Jul '23

13 Jul '23

Hello everyone, Once in a while, my server running BaseX will suddenly experience a big spike in write operations, the hard disk space will fill up to 100%, and the whole server will lock up. I can't say what initiates this, because the logs and metrics disprove every theory I can think of. (There's nothing unusual in the access logs or BaseX data logs, memory usage stays consistently at 45% and CPU usage at 5%, no user attempted anything like a huge bulk upload, etc.) However, one thing that always happens during these incidents is that the Apache error log blows up to a crazy size like 1 GB, filled with the message: PHP Notice: Trying to access array offset on value of type null in /[path]/client/session.php on line 164 This line is in the read method of the Session class from GitHub, and it indicates that the byte position passed to the buffer property is null. My error log probably fills up because read() is called by readString() in a while loop that never terminates. There might be extraordinary circumstances in which during construction, socket_connect returns "true" but the response is not valid or expected. -Tamara -- Tamara Marnell Program Manager, Systems Orbis Cascade Alliance (orbiscascade.org <https://www.orbiscascade.org/>) Pronouns: she/her/hers

2 5

sequences after the path operator
by Graydon Saunders 07 Jul '23

07 Jul '23

Hello -- Using BaseX 10.6, the test query let $test as xs:string := "And O Lord the pride of man, broken in the dust again" let $syntax1 as xs:string := analyze-string($test,'\p{Lu}')/(fn:match/concat('[',.,']'),fn:non-match/string()) => string-join('') let $syntax2 as xs:string := analyze-string($test,'\p{Lu}')/*/(self::fn:match/concat('[',.,']'),self::fn:non-match/string()) => string-join('') return ($syntax1,$syntax2) produces [A][O][L]nd ord the pride of man, broken in the dust again [A]nd [O] [L]ord the pride of man, broken in the dust again I'm surprised by this, because I expected document order to apply to the result of analyze-string and for syntax1 to work in the sense of having the results emerging in the same order as the input. Have I miscomprehended something? Anyone care to have a go at explaining why syntax1 doesn't maintain the order of the input? (I'm possibly mistakenly confident that I understand why syntax2 does.) Thanks! Graydon -- Graydon Saunders | graydonish(a)fastmail.com Þæs oferéode, ðisses swá mæg. -- Deor ("That passed, so may this.")

2 2

Apparent bug when setting @xml:base on element with @base
by Eliot Kimber 07 Jul '23

07 Jul '23

This XQuery demonstrates the problem: (:--------:) let $xmlBaseAtt as attribute() := attribute {'xml:base'}{'/foo/bar.xml'} let $transformed1 as element() := try { $doc1 transform with { insert node $xmlBaseAtt into .} } catch * { <error code="{$err:code}" desc="{$err:description}" object="doc1"/> } let $transformed2 as element() := try { $doc2 transform with { insert node $xmlBaseAtt into .} } catch * { <error code="{$err:code}" desc="{$err:description}" object="doc2"/> } return ( ``[No @base attribute:]`` ,$transformed1 ,``[Has @base attribute:]`` ,$transformed2 ,() ) (:--------:) The results I get with 10.6 are: No @base attribute: <root xml:base="/foo/bar.xml"/> Has @base attribute: <error code="err:XUDY0021" desc="Duplicate attribute name: xml:base." object="doc2"/> It looks like the transform processor is matching @xml:base to @base even though they are different attributes. Is this a bug or is there a different way I should be specifying the @xml:base attribute? This is an issue because @base is a DITA-defined attribute that occurs on elements on which I need to set @xml:base (which is how I found the problem). Cheers, 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>

2 1