BaseX-Talk February 2021

basex-talk@mailman.uni-konstanz.de

10 participants
17 discussions

Jobs and file modules
by Tim Thompson 16 Feb '21

16 Feb '21

Hello, I was experimenting with the jobs module and wondering why there's a difference between *file:write() *and *file:write-text()* in the query below: for $i in 1 to 5 return ( jobs:eval(' declare variable $iter external; file:write-text("~/Desktop/job"|| $iter ||".txt", (prof:sleep(5000), string(current-dateTime()))) ', map {"iter": $i} ) ) With *file:write-text()*, if I don't wrap *current-dateTime()* in *string()*, nothing is written and no files are created. With *file:write()*, text is always written and files always get created. Thanks! Tim -- Tim A. Thompson Metadata Librarian Yale University Library

2 6

Feature requests: Backups, Indexes, Execution Times
by BIRKNER Michael 12 Feb '21

12 Feb '21

Hello BaseX-Community, I am working a while with BaseX now and I like it very much. I think it is a great piece of software ... and it's Open Source ... WOW!!! But every now and then I discover some small cumbersome issues that could maybe solved with some new functionalities. That is why I would like to propose the following features for BaseX: * Description for database backups: Right now, the titles of database backups are like "dbname-2021-02-02-17-45-44". It would be great if one could add a description to such a backup. The reason is: While developing I often update databases step by step and in between these steps, I make backups of the whole database, so in case of errors or if I have to look up something, I could revert to a former state of the database. With a meaningful description, it would be much easier to pick the right backup. * RegEx in index searches: It would be great to have the possibility to search for RegEx patterns in the index, e. g. like this: db:text("db-name", "REGEX-PATTERN-HERE") or db:attribute("db-name", "REGEX-PATTERN-HERE") * Index searches with a path: I sometimes had the need to do an index search within only a certain path, e. g.: db:text('db-name', '/PATH/WITHIN/DB', 'search-word') I don't know if this is even possible to realize, but if yes, it would sometimes be very useful to me. * Selective indexing based on attribute values: It would be great to have selective indexing based on attributes and their values. Imagine an XML structure like this: <items> <item name="id">ABC</item> <item name="title">XYZ</item> <item name="person">Jane Doe</item> ... </items> If one would like to index e. g. only the ID values, a functionality to do selective indexing just for "<item>" nodes with attribute "name" that contains the value "id" would be useful. This would allow to have a comparatively small index for very large XML data sets, which could have impact on query performance. * Human readable execution times in GUI: Maybe a small change but - at least in my case - it would make developing performant xQueries much easier: Having the "Timing" section in the Info-View of the GUI display human readable times. Right now, the values are displayed only in milliseconds like 175713.28 ms. But an additional display in a more human readable format, e. g. hh:mm:ss.ms would sometimes be very useful. I hope at least some of the mentioned features do make sense and will be considered for implementation [:-)] Best regards, Michael Dieses Mail ist ausschließlich für die Verwendung durch die/den darin genannten AdressatInnen bestimmt und kann vertrauliche bzw rechtlich geschützte Informationen enthalten, deren Verwendung ohne Genehmigung durch den/ die AbsenderIn rechtswidrig sein kann. Falls Sie dieses Mail irrtümlich erhalten haben, informieren Sie uns bitte und löschen Sie die Nachricht. UID: ATU 16209706 I https://wien.arbeiterkammer.at/datenschutz

3 4

xquery:eval() required in replace()?
by Graydon Saunders 06 Feb '21

06 Feb '21

Hello -- So as part of building tests, I'm regularizing the text contents of some Word documents into single strings. (Which makes it relatively easy to make sure no words have gotten lost or changed order when compared to other stages of the process.) Regularization is a tactful way to put this particular atrocity: let $stringTidy as function(xs:string+) as xs:string := function($in as xs:string+) as xs:string {$in => string-join(' ') => replace(xquery:eval($menuMatch),'') => replace('
',' ') => replace('	',' ') => replace('',' ') => replace('\p{Zs}',' ') => replace(' +',' ') => replace(' ([,\.;:])','$1') => replace('^ ','') => replace(' $','')} $menuMatch gets stripped out of the Word because it's added by processing, rather than being present in the source file which generates the other half of the compare. (It's currently U+1405, ᐅ, though I devoutly hope this doesn't matter!) It gets read from an XSL source document, which I've included in minimal form, along with some sample data and a minimal-ish query. If I use $menuMatch in the replace, it doesn't work, in the sense that the ᐅ character is NOT removed from the string. If I xquery:eval() it, as here, the replace does work to remove the ᐅ from the string. I don't expect to need xquery:eval to use a variable as the second argument of replace(). Am I wrong? Has the pile of arrow operators exceeded the bounds of reason? Thanks! Graydon

3 2

Re: [basex-talk] FLOATS
by Christian Grün 06 Feb '21

06 Feb '21

Hi Adam, It’s recommendable to use xs:decimal instead of xs:float. Here’s one solution… declare function local:sumVec($seq) { let $count := max(($seq ! string() ! replace(., '[^_]', '') ! string-length())) + 1 let $sums := ( for $c in 1 to $count return sum( for $item in $seq let $tokens := tokenize(string($item), '_') return try { xs:decimal($tokens[$c]) } catch * { 0 } ) ) return string-join($sums, '_') }; …and another one (presumably more cryptic): declare function local:sumVec($seq) { let $numbers := ( for $item in $seq return array { for $token in tokenize(string($item), '_') return try { xs:decimal($token) } catch * { 0 } } ) return string-join( for $c in 1 to max($numbers ! array:size(.)) return sum($numbers[array:size(.) >= $c]?($c)) , '_') }; Hope this helps, Christian

1 0

Re: [basex-talk] BaseX-Talk Digest, Vol 134, Issue 3
by Kourouma Ismael 06 Feb '21

06 Feb '21

Hi, Please, how these queries should be helpful in my journey for learning BaseX ? Best regards, Ismael Send BaseX-Talk mailing list submissions to basex-talk(a)mailman.uni-konstanz.de To subscribe or unsubscribe via the World Wide Web, visit https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk or, via email, send a message with subject or body 'help' to basex-talk-request(a)mailman.uni-konstanz.de You can reach the person managing the list at basex-talk-owner(a)mailman.uni-konstanz.de When replying, please edit your Subject line so it is more specific than "Re: Contents of BaseX-Talk digest..." Today's Topics: 1. Re: Feature requests: Backups, Indexes, Execution Times (Christian Gr?n) ---------------------------------------------------------------------- Message: 1 Date: Sat, 6 Feb 2021 11:12:01 +0100 From: Christian Gr?n <christian.gruen(a)gmail.com> To: Graydon Saunders <graydonish(a)gmail.com> Cc: BIRKNER Michael <Michael.BIRKNER(a)akwien.at>, "basex-talk(a)mailman.uni-konstanz.de" <basex-talk(a)mailman.uni-konstanz.de> Subject: Re: [basex-talk] Feature requests: Backups, Indexes, Execution Times Message-ID: <CAP94bnN_4iLWvPG+S3C068jPx=0QXH_d1OtZrwJ+RLH-frAC6A(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Execution times will now be shown in the MM:SS.mm or HH:MM:SS.mm format, but only? ? in the header of the info view, and ? if the measured time exceeds 60 seconds. A new snapshot is available [1]. Have fun, Christian [1] https://files.basex.org/releases/latest/ On Thu, Feb 4, 2021 at 6:15 PM Graydon <graydonish(a)gmail.com> wrote: > > On Thu, Feb 04, 2021 at 05:21:24PM +0100, Christian Gr?n scripsit: > > > - *Human readable execution times in GUI*: Maybe a small change but > > > - at least in my case - it would make developing performant xQueries > > > much easier: Having the "Timing" section in the Info-View of the GUI > > > display human readable times. Right now, the values are displayed > > > only in milliseconds like 175713.28 ms. But an additional display in > > > a more human readable format, e. g. hh:mm:ss.ms would sometimes be > > > very useful. > > > > > Sounds reasonable and doable. I?ll think about it. > > Please leave the time formatting switchable! I'd strongly prefer > straight milliseconds to a human-readable format. > > -- > Graydon Saunders | graydonish(a)gmail.com > ??s ofer?ode, ?isses sw? m?g. > -- Deor ("That passed, so may this.") End of BaseX-Talk Digest, Vol 134, Issue 3 ******************************************

1 0

Re: [basex-talk] FLOATS
by Adam Law 04 Feb '21

04 Feb '21

Many thanks Christian - I don't know why I didn't think of decimal. I will review my xquery types and arrays. Thanks again - much appreciated :) Adam ! lobotomy() On Thu, Feb 4, 2021 at 11:57 PM Christian Grün <christian.gruen(a)gmail.com> wrote: > Hi Adam, > > It’s recommendable to use xs:decimal instead of xs:float. Here’s one > solution… > > declare function local:sumVec($seq) { > let $count := max(($seq ! string() ! > replace(., '[^_]', '') ! string-length())) + 1 > let $sums := ( > for $c in 1 to $count > return sum( > for $item in $seq > let $tokens := tokenize(string($item), '_') > return try { xs:decimal($tokens[$c]) } catch * { 0 } > ) > ) > return string-join($sums, '_') > }; > > …and another one (presumably more cryptic): > > declare function local:sumVec($seq) { > let $numbers := ( > for $item in $seq > return array { > for $token in tokenize(string($item), '_') > return try { xs:decimal($token) } catch * { 0 } > } > ) > return string-join( > for $c in 1 to max($numbers ! array:size(.)) > return sum($numbers[array:size(.) >= $c]?($c)) > , '_') > }; > > Hope this helps, > Christian > > > > On 2/4/21, Adam Law <adamjameslaw(a)gmail.com> wrote: > > (: > > Hello I have a hopefully not too silly question ... > > Is there an easy way to remove the exponent notation and return > > 30000201_30000000 > > without working out where the E is in the parts and padding zeros > > ====> <a> > > <d>3.0000201E7_3.0E7</d> > > </a> > > :) > > declare function local:sumVec($a,$opt){ > > let $a := <x>{for $w at $pos in $a > > return > > for $v at $pos in tokenize(xs:string($w),"_") > > return element {'a'} { (attribute {'pos'} {$pos}, try > > {xs:float($v)} catch * {0} )} > > }</x> > > let $b := string-join(for $w in distinct-values($a//@pos) > > return if ($opt=0) then sum($a/a[@pos=$w]) ,"_") > > return $b > > }; > > > > let $a := '' > > return <a> > > > > > <d>{local:sumVec(('10000001_10000000','10000000_10000000','10000000_10000000','100_',100),0)}</d> > > </a> > > >

1 0

FLOATS
by Adam Law 04 Feb '21

04 Feb '21

(: Hello I have a hopefully not too silly question ... Is there an easy way to remove the exponent notation and return 30000201_30000000 without working out where the E is in the parts and padding zeros ====> <a> <d>3.0000201E7_3.0E7</d> </a> :) declare function local:sumVec($a,$opt){ let $a := <x>{for $w at $pos in $a return for $v at $pos in tokenize(xs:string($w),"_") return element {'a'} { (attribute {'pos'} {$pos}, try {xs:float($v)} catch * {0} )} }</x> let $b := string-join(for $w in distinct-values($a//@pos) return if ($opt=0) then sum($a/a[@pos=$w]) ,"_") return $b }; let $a := '' return <a> <d>{local:sumVec(('10000001_10000000','10000000_10000000','10000000_10000000','100_',100),0)}</d> </a>

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk February 2021