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

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 27 Aug '20

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

XQDoc Parser requires leading colons in doc-comment for @token documentation
by Andreas Mixich 25 Aug '20

25 Aug '20

Hello, when using `inspect:xqdoc#1` on a module, where the lines of doc comments do not start with a leading colon, as shown by the following example: (:~ Description @comment-token :) the output will be missing the element for the @comment-tokens (i.e.:`xqdoc:function/xqdoc:comment/xqdoc:param`). They only get provided, if the leading colons are set, as in: (:~ : Description : : @comment-token :) Since I dislike to add the leading colons I opened up an issue at [1], but according to Loren Cahlander the parser does not seem to require them. Therefore I assume, that this could be implementation dependent. The spec does not require the leading ':', but it seems, that BaseX does. Could the lack of leading colons be tolerated? That would be nice! Thank you. [1]: https://github.com/xqdoc/xqdoc/issues/4 -- Goody Bye, Minden jót, Mit freundlichen Grüßen, Andreas Mixich

2 2

BaseX GUI: XPath suggestions / completion
by andre.aepli＠gmx.ch 25 Aug '20

25 Aug '20

2 2

improving query performance
by Bill Osmond 24 Aug '20

24 Aug '20

Hi all, I'm attempting to query a fairly large database, with 136,938 resources and a size of 12,257,686,099. The basex server itself is an AWS EC2 instance with 4 cores & 16 gigs of ram, using -Xmx12g. The database contains audio DDEX information which (to me at least) is fairly complicated XML. The query I'm running against the database works and gives me the result I want, but takes upwards of 15 minutes to execute. I've taken a look at the wiki documentation regarding indexes, but it's not clear to me that any of the non-default indexes would help for the query I'm running. That query is: declare namespace ernm="http://ddex.net/xml/ern/411"; for $r in /ernm:NewReleaseMessage for $track_release in $r/ReleaseList/TrackRelease for $party in $r/PartyList/Party for $sound_recording in $r/ResourceList/SoundRecording for $release in $r/ReleaseList/Release where $track_release/ReleaseLabelReference = $party/PartyReference and $track_release/ReleaseResourceReference = $sound_recording/ResourceReference and $track_release/ReleaseResourceReference = $release/ResourceGroup/ResourceGroup/ResourceGroupContentItem/ReleaseResourceReference return <identity> <isrc>{ $track_release/ReleaseId/ISRC/text() }</isrc> <artist>{ fn:string-join($sound_recording/DisplayArtistName, '/') }</artist> <title>{ $sound_recording/DisplayTitleText/text() }</title> <album>{ $release/DisplayTitleText/text() }</album> <icpn>{ $release/ReleaseId/ICPN/text() }</icpn> <sublabel>{ $party/PartyName/FullName/text() }</sublabel> </identity> Am I wrong, and would an additional value index help here? Or is my query just bad? Thanks, Bill p.s. The BaseX GUI client is awesome - especially the treemap view. Really helps with wrangling these XML files!

4 16

Re: [basex-talk] documentation flaw
by Christian Grün 22 Aug '20

22 Aug '20

Hi Rob, you are right. I have replaced "or" with "and". Thanks for the hint. – Best, Christian On Sat, Aug 22, 2020 at 12:57 PM RobStapper <r.stapper(a)lijbrandt.nl> wrote: > Hi, > > > > I have my doubts about the expressions used at the “tertium non > datur”-principle in the documentation [1]. > > Or the expression should be “$a or not($a)” or the rewritten expression > should be “false()” . > > > > [1]: https://docs.basex.org/wiki/XQuery_Optimizations#Pure_Logic > > > > Best regards, > > > > Rob Stapper > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_-2765550508791472733_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >

1 0

documentation flaw
by RobStapper 22 Aug '20

22 Aug '20

Hi, I have my doubts about the expressions used at the “tertium non datur”-principle in the documentation [1]. Or the expression should be “$a or not($a)” or the rewritten expression should be “false()” . [1]: https://docs.basex.org/wiki/XQuery_Optimizations#Pure_Logic 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

1 0