BaseX-Talk

basex-talk@mailman.uni-konstanz.de

12 participants
5242 discussions

Simple xqdoc to HTML converter
by Omar Siam 15 Mar '21

15 Mar '21

Hi, I brushed up the 2006 xqdoc to HTML XQuery a bit to document some of my code. Maybe this is also interesting to others. https://github.com/acdh-oeaw/xqdoc I also found https://github.com/lcahlander/xqDoc-eXist-db mentioned on this mailing list. I plan to look into getting this to work on BaseX. Best regards Omar Siam

3 2

Options for ft:search
by Sebastian Zimmer 15 Mar '21

15 Mar '21

Hi, I'd like to request a feature concerning the ft:search method: An `lserror` option that works exactly like the global option `LSERROR`. It would be nice if we could set the maximum Levenshtein distance specifically for each fuzzy search without having to adjust the global option. Another question on ft:search: Is there a reason why it doesn't have a `case` option just like ft:contains has one? Best regards, Sebastian

2 3

Histogramming a large dataset
by Ron Katriel 10 Mar '21

10 Mar '21

Hi, I would appreciate your advice on optimizing a query against a large BaseX (9.2.4) database. It is loaded with data from the FDA’s Adverse Event Reporting System (FAERS). Currently this is just the 2020 dataset which comprises 12 documents stored as 308,870,597 nodes (6,565 MB). The queries below effectively - though not necessarily efficiently - implement a histogram. The first, which is applied to patient gender (sex), returns the results (3 items) in 52 seconds: 2 893694 1 583999 0 198 The second does this for patient weight - rounded to the closest 10 lbs increment. It takes 580 seconds to place the data into 67 bins. Initially I tried running it on the rounded weights but aborted the run as it was a taking an inordinate amount of time (there are 217 distinct weights in the dataset). Is there a way to improve the performance of this type of query? Thanks, Ron (: 3 items - 52 sec :) let $safetyreport := db:open('FAERS')/ichicsr/safetyreport for $value in distinct-values($safetyreport/patient/patientsex) return concat($value, " ", count(index-of($safetyreport/patient/patientsex, $value))) (: 67 items - 580 sec :) let $safetyreport := db:open('FAERS')/ichicsr/safetyreport for $value in distinct-values($safetyreport/patient/patientweight ! (. div 10.0) ! round(.) ! (. * 10)) return concat($value, " ", count(index-of($safetyreport/patient/patientweight ! (. div 10.0) ! round(.) ! (. * 10), $value))) -- The information in this email and any attachments are intended solely for the recipient(s) to whom it is addressed, and may be confidential and/or privileged. Any unauthorized distribution or copying of this transmittal or its attachments is prohibited. If you are not a named recipient or have received this email in error: (i) you should not read, disclose, or copy it, (ii) please notify the sender of your receipt by reply email and delete this email and all attachments.

3 6

Question about Staircase Join
by Yasir B 03 Mar '21

03 Mar '21

Hello, I am studying the paper "Storing and Querying Large XML Instances". [https://files.basex.org/publications/Gruen%20%5B2010%5D,%20Storing%20and%20…] This is very interesting and helpful to read! I apologize I fail to understand the following in 3.4.2.1 Staircase Join: "In the partitioned plane, the scanned areas are made disjunct, i.e., scanning is canceled whenever the pre value of the currently scanned node equals the pre value of the next context node." Since pre values are unique (?), I couldn't follow how the next context node would have the same pre value. For the partitioning step, I had the impression the next context node is not the same as the current context node, nor would it be a descendant of the current context node. Thank you, Yasir

2 1

map-entries sequence
by Rob Stapper 02 Mar '21

02 Mar '21

Hi Christian, In my casus I’m exporting and importing xQuery maps where the export-format is a xQuery-file or a json-file. Hereby the sequence of the exported map-entries is important: I want the sequence in which the entries are generated to stay in tact when exporting. I can’t get this working. My current work-around is to place the map-entries in an array. It does the trick but it feels redundant. Is there a way to have this kind of control over map-entry sequence? Thnx in advance, Rob Stapper Sent from Mail for Windows 10 -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Write several XML files via one XQuery
by Brune, Nicole 01 Mar '21

01 Mar '21

Dear all, please excuse me if this has been covered in the documentation and I just haven't found it. I am trying to harvest some information from XML files in a database (all XML files) and create several new XML files with the information. I am aware of the function write:file(path, data). Is it possible to write several files in one go and via one XQuery? I have tried exchanging "../test.xml" with "../test[1 to 2000].xml, ..." but, unfortunately, it did not work. Thank you kindly in advance for your help! Best, Nicole

2 1

BaseX 9.5: The Spring Edition
by Christian Grün 25 Feb '21

25 Feb '21

Dear all, we are more than happy to provide you with a new and fresh version of BaseX, our XML framework, database system and XQuery 3.1 processor: https://basex.org/ BaseX is getting faster and faster! We have spent most of our time on query rewritings and optimizations, which will speed up the execution of your XQuery code and RESTXQ apps. You can find various other new enhancements in our release: RESTXQ - the client IP address behind a proxy is added to the logs - stack traces in the error message can now be suppressed - the default error code has been changed from 400 to 500 - error messages are more user-friendly now (#1708) - content negotiation was improved (#1991) - inline arguments of called function (#1982) XQUERY FUNCTIONS - Utility: new functions for sequences, arrays and maps - Higher-Order Functions: hof:drop-while - Jobs: More options for job intervals XQUERY PERFORMANCE - revised scoring propagation (all items will take less memory) - default function inlining limit reduced from 100 to 50 - axis path rewritings, better typing (#1910, #1976, #1979) - better typing (#1906, #1908, #1909, #1944, #1945) - faster data()/string() checks (#1975) - rewrite map:merge to map:put (#1969) - rewrite order by to fn:sort (#1966) - rewrite group by to fn:distinct-values (#1932) - rewrite quantifiers to FLWOR expressions (#1961) - optimizations of arithmetic expressions (#1938, #1972) - optimizations of lookup operator (#1929, #1984) - optimizations of counts (#1965, #1973, #1974) - optimizations of regular lists (#1919, #1924) - optimizations of switch expression (#1920) - optimizations of instance of (#1939) - distinct values (#1930, #1967) - positional checks (#1937) - existence checks (#1971) For a more comprehensive list of added and updated features, check out our documentation (docs.basex.org) and check out the GitHub issues (github.com/BaseXdb/basex/issues). Have fun, Your BaseX Team

3 2

BaseX, xinclude and xpointer
by pascaljoubaud＠gmail.com 19 Feb '21

19 Feb '21

Hello BaseX-Community, I'm a beginner with baseX so my questions may sound a bit weird. I hope not too much. I have a problem using xinclude in a baseX database. Basically i have a main file which contains this xinclude instruction : <xi:include href="EP15.xml" xpointer="element(EP15)"><xi:fallback><p>Pièce non encodée pour le moment.</p></xi:fallback></xi:include> In my baseX database i have my main file and the EP15.xml file which contains this instruction : <div type="Piece" xml:id="EP15">blabla<div> When i 'm looking to my main file in base X, i always have the fallback instruction displayed : <p>Pièce non encodée pour le moment.</p> I'm using baseX 9.3.2., the local option XINCLUDE is turned on. I have also tried to use direct xpath instead of a named element in my xpointer xpointer="element(/TEI/text/body/div[1])"> but the resultat is stille the same I'm a bit stuck at the moment.. Any help would be very much appreciated ! Thanks a lot Pascal

2 10

Nasty trap with RESTXQ content negotiation
by Marco Lettere 19 Feb '21

19 Feb '21

Dear all, First of all, I hope everything is fine and all of you are staying healthy! When I read again the docs about Content Negotiation in RestXQ I noticed the sentence: Functions can be restricted to specific Media Types. The default type is|*/*|. So I wrote the two RestXQ signaures [1] with the expectation of *fallback()* behaving as a catch-all for mime-types not declared in *specific(**)*. At that point, when calling the service with something stating "Content-Type: application/xml" BaseX yields the following error: Stopped at /....: [basex:restxq] Several functions found for path "test": - ccp_ui:test [text/plain] - ccp_ui:test2 [text/plain] If I specify an explicit %rest:consumes("*/*") in the annotations of fallback(), specific() correctly intercepts the request. Unfortunately at that point calling with "Content-Type: text/plain" which should slip through the functions and be catched by fallback() yields instead: No function found that matches the request. So there is no combination, to my knowledge, to implement my use-case correctly ... besides handling mime-types explicitly in code (which is rather uncomfortable). I'm using BaseX 9.4.5 at the moment. Do you have any hint on this? Thank you very much. Marco. [1] declare %rest:path("test") %rest:POST("{$body}") %rest:consumes("text/csv", "application/xml", "application/json") %output:method("text") function s:specific($body as document-node()) { "Treated as document" }; declare %rest:path("test") %rest:POST("{$body}") %output:method("text") function s:fallback($body as item()) { "Treated as binary" };

2 2

vanishing whitespace with fn:doc()
by Jos van den Oever 17 Feb '21

17 Feb '21

Dear all, First off: BaseX is great to work with. I use it for a few statically generated websites. But I recently found what might be a bug. Some whitespace vanishes when loading xml files. E.g. this xml file: ```test.xml <a> a b <a> c </a> d e </a> ``` run like this: doc('test.xml') gives: <a>a b<a>c</a>d e</a> But running this: ``` parse-xml('<a> a b <a> c </a> d e </a>') ``` retains the whitespace. I've tested this with BaseX 7.0, 8.0, 9.0 and 9.4.6. Running this in saxon-he-10.3.jar retains the whitespace. I can work around this issue by placing xml:space="preserve" in the document element. I cannot come up with a scenario in which discarding whitespace during is parsing is ok when no DTD or XML Schema is provided. Best regards, Jos

2 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk