BaseX-Talk February 2018

basex-talk@mailman.uni-konstanz.de

22 participants
23 discussions

Global locks
by Andy Bunce 11 Feb '19

11 Feb '19

Running the following in the GUI (8.6.5) ``` let $db:="BEP" return count(collection($db)) ``` The info windows shows $db is inlined Compiling: - inline $db_0 - pre-evaluate collection("BEP") to document-node() sequence - pre-evaluate count((db:open-pre("BEP",0), ...)) to xs:integer - simplify gflwor Optimized Query: 9193 All good. Submitting a job ``` let $q:='let $db:="BEP" return count(collection($db))' return jobs:eval($q,(),map{"cache":true()})!(jobs:wait(.),jobs:list-details(.)) ``` returns: <job id="job90" type="ScheduledXQuery" state="cached" user="admin" duration="PT0.007S" reads="(global)" writes="(none)">let $db:="BEP" return count(collection($db))</job> Note @reads="(global)" But ``` let $q:='count(collection("BEP"))' return jobs:eval($q,(),map{"cache":true()})!(jobs:wait(.),jobs:list-details(.)) ``` <job id="job92" type="ScheduledXQuery" state="cached" user="admin" duration="PT0.006S" reads="BEP" writes="(none)">count(collection("BEP"))</job> Note @reads="BEP" Is this correct and/or of any consequence? /Andy

2 8

9.0?
by Marco Lettere 01 Mar '18

01 Mar '18

Hi Christian & team, since XML Prague 18 is approaching I remembered that there used to be this wonderful habit of releasing a new BaseX version for the event :-). I am wondering whether there are any timing plans for the 9.0 release. In particular we are eager to test the new features [1] and [2]. Thank you for any updates on the matter and please continue with your incredible work! Best regards, Marco. [1] https://github.com/BaseXdb/basex/issues/1498 (persistent jobs) [2] https://github.com/BaseXdb/basex/issues/1449 (websocket support)

2 2

Signature of db:add
by Tim Thompson 28 Feb '18

28 Feb '18

Hello, The two argument signature of the db:add function does not seem to work ( http://docs.basex.org/wiki/Database_Module#db:add). Is this still valid in BaseX? When I try something like db:add("test", <test/>), I get an error: [FODC0007] Resource path '' is invalid. Thanks! -- Tim A. Thompson Discovery Metadata Librarian Yale University Library

2 1

Whitespace chopping / option -w
by Hans-Juergen Rennau 27 Feb '18

27 Feb '18

Dear BaseX team, "whitespace chopping" (which happens by default unless command-line option -w is used) does not only remove "whitespace-only" text nodes, but also leading/trainling whitespace in element content, for example: doc.xml:<hello> BaseX is phantastic! </hello> basex -i doc.xml . => <hello>BaseX is phantastic!</hello> While the result is of course true, I regard leading/trailing whitespace in element content as information which has a different "level of significance" than whitespace-only text nodes. In other words: I think it is an important use case that leading/trailing whitespace must be preserved, while the "pretty print whitespace" should be discarded. Did I overlook a way to get rid of whitespace-only text nodes without touching leading/trailing whitespace in element content? If not, it would be wonderful if you added a new option doing just that. With kind regards -Hans-Jürgen

1 0

Update Module question: update:apply
by Bridger Dyson-Smith 26 Feb '18

26 Feb '18

Hi all -- I was working with the update:apply example [1], and it throws an error: [XPTY0004] Cannot convert xs:string to node(): "doc.xml". I'm a little confused by this: if I modify the example, and change the last to `db:add('existing-db', 'doc.xml')` (which is db:add#1, right?), it works fine. However, keeping the local:update and trying to use `db:add#1` generates another error: [XPST0017] db:add(database,input[,path[,options]]): 1 argument supplied, 2-4 expected Would someone be able to shed some light on where this is going wrong? Thanks, Bridger [1] http://docs.basex.org/wiki/Update_Module#update:apply

2 2

Re: [basex-talk] bug in XSLT
by Kristian Kankainen 24 Feb '18

24 Feb '18

2 1

bug in XSLT
by nikos dimitrakas 23 Feb '18

23 Feb '18

There seems to be a problem when using baseX to create html with XSLT. Saxon seems to add a META-tag if the head-tag is present. But it is not <meta/>. It is instead <meta> (without closing tag, which is ok in html) and this causes baseX to give an error: The element type "META" must be terminated by the matching end-tag "</META>". With the newer version of Saxon the error is the same but the case has been changed to <meta> instead of <META>. This can be easily reproduced with the following query: let $s := <xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="html"/> <xsl:template match="/"> <html><head/><body/></html> </xsl:template> </xsl:transform> return xslt:transform(/, $s) In the new XSLT version there is an option to set the output to xhtml and that works, but the html output (which is the only available option in XSLT 1) fails. The generated meta tag seem to be this <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> I have even tried to override this by specifying that meta tag myself with closing tag but that does not work. I even tried setting the attribute include-content-type in the xsl:output, but it had no effect. Setting the output method to xml would work if the html genererated is in fact correct xml (like in the example above). Output metod "text" seems to also behave strangely. Maybe BaseX ignores the output method and tries to treat everything as xml? /nikos

1 0

BaseX not running
by Leo Studer 21 Feb '18

21 Feb '18

Hello I try desperately getting baseX 8.6.7 to run on MacOS X 10.13.3 where I have Java 9 installed Here the error message: BaseX installed with homebrew today: MBP-2015:~ leo$ basexgui WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX (file:/usr/local/Cellar/basex/8.6.7/libexec/BaseX.jar) to method com.apple.eawt.Application.getApplication() WARNING: Please consider reporting this to the maintainers of org.basex.gui.GUIMacOSX WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Failed to initialize native Mac OS X interface MBP-2015:~ leo$ and the same error with the Jar file Last login: Wed Feb 21 18:16:27 on ttys001 MBP-2015:~ leo$ java -jar ~/Downloads/BaseX867.jar WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.basex.gui.GUIMacOSX (file:/Users/leo/Downloads/BaseX867.jar) to method com.apple.eawt.Application.getApplication() WARNING: Please consider reporting this to the maintainers of org.basex.gui.GUIMacOSX WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Failed to initialize native Mac OS X interface MBP-2015:~ leo$ Any suggestions? Thanks for caring Always Leo

2 1

inspect:functions does not return updating functions
by Rob Stapper 21 Feb '18

21 Feb '18

Hi Christian, After a period of focussing on Angular I'm back at to BaseX ;-). I found that the inspect:functions function does not return updating functions. Is that by design? I would like to be able to use the inspect:functions function for triggering my update function on the server side, which of course are updating functions TIA for you reply, Cheers, Rob Stapper

3 7

oXygen XML, content negotiation and #1220
by Omar Siam 20 Feb '18

20 Feb '18

Hi list! I like my oXygen editor to request raw XML data from my RESTxq endpoints to test XSL stylesheets. When I do this with RESTxq paths that have different %rest:produces it fails with the BASX0003 multiple functions error. Turns out oXygen sends application/xml, */* as Accept header without any quality. I understand that as documented in https://github.com/BaseXdb/basex/issues/1220 this is known not to work. My/our workaround is to branch in a single XQuery function using sth. like: if (some $a in tokenize(request:header("ACCEPT"), ',') satisfies $a = ('text/xml', 'application/xml')) then $xml else $xhtml I hope this is still on the agenda for 8.7. Best regards Omar Siam

3 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk February 2018