BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

Question about map:merge
by Markus Schmid 03 Sep '20

03 Sep '20

Hi, I have a small code sample ScriptOrig.xqy (https://gitlab.com/ms452206/stackoverflow63684864). I am not sure what is wrong. While I expected this output: <database name="DS0002" autosar="AutosarFoo02.arxml" fibex="FibexFoo02.xml"/> <database name="DS0003" autosar="AutosarFoo03.arxml" fibex="FibexFoo03.xml“/> I got this: <database name="DS0002" autosar="AutosarFoo02.arxml" fibex=""/> <database name="DS0003" autosar="AutosarFoo03.arxml" fibex="“/> The modified version ScriptModified.xqy works as required. You can reproduce this using BaseX 9.4.2. I have more weird function using map:entry. Thank you for exploring this. Markus

2 3

ancestor axis i.c.w. fetched XML issue
by RobStapper 31 Aug '20

31 Aug '20

Hi Christian, I encountered some inconsistency when using an fetched XML-node in combination with xpath’s ancestor-axis. I attached a small snippet. I expect an ancestor here. It works alright if the XML-node is not fetched from a document or in case of the parent-axis. Best 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

3 8

json:doc-available()
by Hans-Juergen Rennau 30 Aug '20

30 Aug '20

Dear BaseX team, it's really great that now we have functions json:doc(), csv:doc() and html:doc(). In my opinion it becomes increasingly obvious that BaseX is a powerful data integration platform. Perhaps you will also add the corresponding xxx:doc-available() functions? Kind regards,Hans-Jürgen

2 1

superfluous shape="area' when using html:parse()
by Jos van den Oever 30 Aug '20

30 Aug '20

Hi all, When loading a document with html:parse(), an extra attribute is added to every <a/> element. <a href="abc"></a> becomes <a shape="rect" href="abc"></a> This error is even shown in the example on the wiki: https://docs.basex.org/wiki/HTML_Module It turns out this behaviour can be avoided by using the 'nodefaults" option of TagSoup: html:doc($uri, map { 'nodefaults': true() }) That's a lot faster than removing these attributes from loaded document. ⤳Jos

2 1

Re: [basex-talk] [EXTERNAL] - Re: XQExpression-8.executeQuery() API throws java.lang.NullPointerException exception while executing XQuery(retrieving the 171 MB xml document) like db:open('testenvSSL1', '6300000180000114/0600000180002931.xml')
by Christian Grün 28 Aug '20

28 Aug '20

Exactly; it’s called Client API in the documentation: https://docs.basex.org/wiki/Java_Examples Srikumar Choudhury <schoudhu(a)opentext.com> schrieb am Fr., 28. Aug. 2020, 07:33: > Hi Christian, > Are you talking about BasexClient as mentioned in > below link? is this BaseX API? > > > https://github.com/BaseXdb/basex/blob/master/basex-examples/src/main/java/o… > Thanks, > Srikumar > ------------------------------ > *From:* Christian Grün <christian.gruen(a)gmail.com> > *Sent:* Thursday, August 27, 2020 7:57 PM > *To:* Srikumar Choudhury <schoudhu(a)opentext.com> > *Cc:* BaseX <basex-talk(a)mailman.uni-konstanz.de>; Rajiv Pandya < > rpandya(a)opentext.com>; Sharath Babu Pulumati <spulumat(a)opentext.com> > *Subject:* Re: [EXTERNAL] - Re: XQExpression-8.executeQuery() API throws > java.lang.NullPointerException exception while executing XQuery(retrieving > the 171 MB xml document) like db:open('testenvSSL1', > '6300000180000114/0600000180002931.xml') > > …and our own API will definitely consume less memory. Did you try it as > well? > > > > On Thu, Aug 27, 2020 at 2:55 PM Christian Grün > <christian.gruen(a)gmail.com> wrote: > > > > > do I need to increase -Xmx4096m to higher? > > > > +1 >

1 0

27 Aug '20

> do I need to increase -Xmx4096m to higher? +1

1 1

Unpredictable function return types seems to default to item()? instead of item()*. Applies to 9.4.2
by Wiemer, Sebastian 27 Aug '20

27 Aug '20

Hi, Thank you Christian for the new 9.4.2. release! The function "f()" below will yield to the error: "Cannot promote item()? to xs:integer?: $result_4" This works in BaseX 9.1 ------ declare function local:f() as xs:integer()*{ let $id := client:connect("localhost", 1984, "admin", "admin") let $result := client:query($id, "1,2") let $close := client:close($id) return $result }; local:f() ----- I guess, that unpredictable return types at compile time default to item()? instead of item()* and thus cannot be used in a function returning anything else but item()? Has someone an idea for a solution/workaround for this? Best regards, Sebastian Eine Studie. Über 1300 Befragte. Ein Thema: Künstliche Intelligenz. https://ki.adesso.de/de/erste-schritte/index.html?pk_campaign=KI%20Report&p… ------------------------------------------------------- >>> business. people. technology. <<< ------------------------------------------------------- adesso SE mit Sitz in Dortmund Vorstand: Michael Kenfenheuer (Vors.), Dirk Pothen, Andreas Prenneis, Stefan Riedel, Jörg Schroeder Vorsitzender des Aufsichtsrates: Prof. Dr. Volker Gruhn Amtsgericht Dortmund HRB 20663

2 2

Xquery performence
by chandra sekhar n 27 Aug '20

27 Aug '20

Dear Basex team, We are facing an xquery performance issue. Please find the query in below and please suggest any clue to optimize query let $subbrk := (collection("867509_Voice_DECEMBER-19_Billed_1")/SUBCUSTBRK) let $detailUsageTxn := $subbrk/DETAIL/TRANSACTION[@Usage = 'usage'] let $DistCallTypesAll := ($detailUsageTxn/SUB_SECTION/@Type) let $DistCallTypes := ( for $r in $DistCallTypesAll group by $ct := $r return $ct) *//Here taking nearly 3 minutes* let $allmonths := distinct-values($subbrk/Month) let $rowcnt := count($detailUsageTxn/SUB_SECTION) let $months := $allmonths[position() le 10000] let $opttype := 'NumVal' let $durop := 'hh:mm:ss' return ( if($DistCallTypes!='' ) then( for $month in $months return <R> <GRPBY>{ $month }</GRPBY>{ if($opttype = 'NumVal') then for $ct in $DistCallTypes let $ctCnt := sum($detailUsageTxn/SUB_SECTION[data(@Type) = data($ct) and data(../../../Month) = $month]/@Calls) *//Here taking 4 to 5 minutes* return element { replace(concat('_',data($ct)),'(\.|\[|\]|\\|\||\-|\^|\$|\?|\*|\+|\{|\}|$|$| |')', '_') } {xs:decimal($ctCnt)} else () } </R>) else() ) Regards, Chandrasekhar

2 2

Re: [basex-talk] BaseX - CORS
by Andy Bunce 27 Aug '20

27 Aug '20

Hi Elina, (cc: basex-talk) Happy to help. That email correspondence is a bit old, and the code referenced is ancient. I suspect your problems creating the headers in XQuery restxq are due to default namespace prefix changes, rest vs restxq, way back when. You are correct that enabling the supplied CORS filter in web.xml works for GET and POST but not PUT. The reason is that PUT is not in the default AllowedMethods [1] As an exercise I have created a little sample that uses only RESTXQ facilities. [2] It assumes the web.xml CORS filter is not enabled. As supplied it has: A cors.html file, to be opened directly in the browser, i.e. using the file protocol. A cors.xqm intended to be put in the webapp folder of a local basexhttp running on 8984 Only the PUT request is allowed as I have commented out the Xquery generation of the CORS headers for GET and POST. Note PUT is a non-simple CORS request and will result in the browser sending an additional request using the OPTIONS method [3] This can be seen in the screenshot and is handled in the cors.xqm code. Hope this helps /Andy [1] https://www.eclipse.org/jetty/documentation/current/cross-origin-filter.html [2] https://gist.github.com/apb2006/ea6a901a570b04f94e0e0e21098a5402 [3] https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#Preflighted_requests [image: image.png] On Fri, 7 Aug 2020 at 13:53, Elina Koskentalo <ekoskent(a)gmail.com> wrote: > Hello Andy, > > I hope you don't mind me contacting you, I found this email corresponding > between you and another person about BaseX and adding > the Access-Control-Allow-Origin header to the response. > https://mailman.uni-konstanz.de/pipermail/basex-talk/2017-February/011782.h… > > I have a very similar issue than what you are talking about there. I don't > manage to define a rule in the restxq file that would simply add > Access-Control-Allow-Origin header to or requests. I already manipulated > the filters in the web.xml file which now works for GET but for PUT I still > get the CORS issue back. > > Would you have any tips for me? Thank you very much in advance! > > Best regards, > Elina Koskentalo > ekoskent(a)gmail.com >

3 4

Stack Overflow on 9.4.2
by AirQuick 25 Aug '20

25 Aug '20

This `test.xq` file works on BaseX 9.4.1: ``` xquery version "3.1"; import module "urn:x-xspec:common:deep-equal" at "https://github.com/xspec/xspec/raw/c629869560ab2bce3a6199569917de70ede4bbc3…"; let $r := Q{urn:x-xspec:common:deep-equal}deep-equal((), (), '') return element test { $r } ``` $ BaseX941/basex/bin/basex test.xq /tmp/BaseX941/basex/.basex: writing new configuration file. <test>true</test> But it fails on 9.4.2: $ BaseX942/basex/bin/basex test.xq /tmp/BaseX942/basex/.basex: writing new configuration file. [basex:overflow] Stack Overflow: Try tail recursion? Is it possibly a regression in 9.4.2? -- AirQuick

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk