BaseX-Talk

basex-talk@mailman.uni-konstanz.de

7 participants
5254 discussions

Parallelizing writes to a database
by Eliot Kimber 18 Apr '25

18 Apr '25

In my Mirabel system, I create a link database that records all the links made in a set of documents. This becomes a “where used” index over the content. We have on the order if 200K links for one content set, so at 0.1 second per link it takes about 7 hours to build this index. I’m currently doing this in one process that builds the whole index and then stores it in a database. This is failing in hard-to-diagnose ways, for example, because a database has a write lock on it when I go to rename it from it’s temp name to it’s production name (to replace the current production version). The data is such that I could parallelize the processing but I’m not sure how I would do that in BaseX so that I can safely write to a single database from multiple threads. The fork-join() docs clearly say “non-updating” functions, so that doesn’t seem to be an option. I have multiple BaseX HTTP servers running so I could farm processing across them, but I think I would then run into write lock issues. I could create separate databases for each thread of operation and then combine those at the end—that seems like it might be the best option. Have I missed anything? Thanks, Eliot _____________________________________________ Eliot Kimber Sr. Staff Content Engineer O: 512 554 9368 servicenow servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | X<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Instagram<https://www.instagram.com/servicenow>

1 0

Bug report - argument = context item, param value several items
by Hans-Juergen Rennau 10 Apr '25

10 Apr '25

Dear BaseX people, I have encountered a bug (?). Please consider this code: = = = = = = = = = begin = = = declare namespace f="http://weatherreport.org/heavyweather"; declare function f:relatedNames($node, $relationship) as xs:string* { let $fnName := function($node) { let $_DEBUG := trace(count($node), '#node: ') return name($node)} let $items := switch($relationship) case 'child' return $node/* default return error() return $items/$fnName(.) => distinct-values() => sort() => string-join(', ')}; let $doc := <doc><a/><b/><c/></doc>return f:relatedNames($doc, 'child') = = = = = = = = = end = = = = = = = = = = = = output = = =#node: 3Stopped at C:/projects/foxpath-examples/pre-balisage/problem-basex2.xq, 15/25:[XPTY0004] Item expected, sequence found: (<a/>, <b/>, <c/>).= = = = = = = = = = = = = = = = The call $fnName(.) receives a single item, but three items arrive at the function item! With kind regards,Hans-Jürgen PS: The funny switch() seems to play a part in the game, when I removed it, the issue vanished.PPS: BaseX 11.8 [Standalone]

2 3

Execution of let clauses versus optimization
by Hans-Juergen Rennau 06 Apr '25

06 Apr '25

Dear BaseX people, I observe a behaviour which appears to me not desirable, although it is, strictly speaking, correct. Please consider this code: let $fnCopy := function($term) {trace('yes', 'within fnCopy: ')} let $_DEBUG := trace('before call fnCopy') let $result := $fnCopy('yogi') (: let $_DEBUG := if ($result eq 'NEVER') then error() else () :) let $_DEBUG := trace('after call fnCopy') return () As long as the commented out clause is not activated, the function is *not* executed. It is strictly speaking correct behaviour: the processor may optimize and skip the call of $fnCopy, as it does not contribute to the value of the containing FLWOR expression. However, when using functions with side-effects (as file:write()), it is of course necessary to be sure that the call is executed. Contrary to other processors, according to my experience BaseX has never skipped let clauses for reasons of optimization, and in many years of usage I have again and again highly appreciated this behaviour. The skipping behaviour is new to me. Is it so that BaseX has changed its policy concerning let clauses not contributing to the FLWOR result? It would be very important to know, because the execution of functions with side effects is everyday practice. Kind regards,Hans-Jürgen

2 2

11.8: Store always clearing on restart
by Zimmel, Daniel 26 Mar '25

26 Mar '25

Hi, is this a bug? The store is always clearing on restart. In contrast, the documentation says: "The store will still be available if BaseX is restarted until it is cleared." https://docs.basex.org/main/Store_Functions It works as documented in 11.6, but not in 11.7 and 11.8. Steps to reproduce via GUI: 11.6: Start GUI XQuery: store:put('TEST','TEST') Close GUI Start GUI XQuery: store:get('TEST') Result: 'TEST' 11.7/8: Start GUI XQuery: store:put('TEST','TEST') Close GUI Start GUI XQuery: store:get('TEST') Result is empty The changelog for 11.7 says (not related?): [MOD] Store functions: only read if contents have changed (https://basex.org/2025/01/31/basex-11.7/) Cheers, Daniel

2 3

Re: document-uri() and base-uri() functions in BaseX 11.8
by ykhabins＠bellsouth.net 25 Mar '25

25 Mar '25

Hi Gunther, I tested the latest build, BaseX 11.9 beta c55e0e8 Everything is back to normal. The document-uri() and base-uri() functions working as expected. Thanks a lot for such quick turn-around with the fix. Regards, Yitzhak Khabinsky

1 0

Re: document-uri() and base-uri() functions in BaseX 11.8
by ykhabins＠bellsouth.net 25 Mar '25

25 Mar '25

Hi Gunter, I tested the latest build, BaseX 11.9 beta c55e0e8 Everything is back to normal. The document-uri() and base-uri() functions working as expected. Thanks a lot for such quick turn-around with the fix. Regards, Yitzhak Khabinsky

1 0

document-uri() and base-uri() functions in BaseX 11.8
by ykhabins＠bellsouth.net 25 Mar '25

25 Mar '25

Hello, Congrats on the BaseX 11.8 release. Was there a change in BaseX 11.8 to the document-uri() and base-uri() functions behavior? It seems that they are striping out a file name at the end of the fully qualified file path on the file system! Please find below a repro of it. BaseX 11.7 ========== declare variable $base_dir as xs:string := 'e:\Temp\Identity Transformation88\'; for $x at $i in collection($base_dir) let $file := tokenize(document-uri($x), '/')[last()] return (document-uri($x), $file) Emits the following as expected: file:///E:/Temp/Identity%20Transformation88/Input.xml Input.xml file:///E:/Temp/Identity%20Transformation88/Output.xml Output.xml BaseX 11.8 ========== The same XQuery emits the following: file:///E:/Temp/Identity%20Transformation88/ file:///E:/Temp/Identity%20Transformation88/ Regards, Yitzhak Khabinsky

2 2

Pretty printing of results in BaseX GUI.
by Buddy Kresge 25 Mar '25

25 Mar '25

In BaseX GUI (Version 10.5), I cannot get the pretty printing to work. I have the below option configured in .basexgui but it appears to have no impact, as the XML that is output in the Results area is NOT pretty printed. Can you advise on how to best get the pretty printing of the XML to happen in BaseX GUI? # Local Options SERIALIZER = indent=yes Buddy Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

2 4

Great work! Thank you basex folks
by Liedtke, Alexander 23 Mar '25

23 Mar '25

Thanks for the great work and the new version update! I think everybody using basex should consider using the (pretty good hidden) donate button at the bottom of the basex.org homepage, to at least spend the devs a good weekend with coffee or beer… 😉

2 2

csv:parse header option not working in version 11.7
by Lizzi, Vincent 20 Mar '25

20 Mar '25

Hi BaseX team, Has the "header" option on csv:parse changed between BaseX version 11.6 and 11.7? Here is an example to illustrate what looks like a problem or change. Given a tab separated text file such as this: aaaa bbbb cccc a1 b1 c1 a2 b2 c2 This query uses the "header": "yes" option on csv:parse which should map column names to element names. "tsv-test.tsv" => file:resolve-path() => file:read-text() => csv:parse(map{'separator': 'tab', 'header': 'yes'}) BaseX version 11.6 produces the expected parse: <csv> <record> <aaaa>a1</aaaa> <bbbb>b1</bbbb> <cccc>c1</cccc> </record> <record> <aaaa>a2</aaaa> <bbbb>b2</bbbb> <cccc>c2</cccc> </record> </csv> BaseX version 11.7 seems to be ignoring the header option and produces this output: <csv> <record> <entry>aaaa</entry> <entry>bbbb</entry> <entry>cccc</entry> </record> <record> <entry>a1</entry> <entry>b1</entry> <entry>c1</entry> </record> <record> <entry>a2</entry> <entry>b2</entry> <entry>c2</entry> </record> </csv> If this is an expected change, is there any equivalent to the option "header": "yes" ? Best regards, Vincent ______________________________________________ Vincent M. Lizzi Head of Information Standards | Taylor & Francis Group E-Mail: vincent.lizzi(a)taylorandfrancis.com<mailto:vincent.lizzi@taylorandfrancis.com> Web: www.tandfonline.com<http://www.tandfonline.com/> Time zone: US Eastern Taylor & Francis is a trading name of Informa UK Limited, registered in England under no. 1072954 "Everything should be made as simple as possible, but not simpler." Information Classification: General

3 4

← Newer
1
2
3
4
5
6
7
8
9
...
526
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk