BaseX-Talk April 2017

basex-talk@mailman.uni-konstanz.de

18 participants
21 discussions

Preparing BaseX 8.5.4 (please don't forget Issue #1341)
by Jan Dölle 20 Feb '18

20 Feb '18

Hi, we noticed you prepare release 8.5.4. Please don't forget to fix issue: SQL with BaseX 8.5.3 #1341 Thx Jan -- Jan Dölle E-Mail: basex-list(a)id1.de Telefon +49-69-244502-0 Home: www.id1.de Information Design One AG, Baseler Straße 10, 60329 Frankfurt am Main Registereintrag: Amtsgericht Frankfurt am Main, HRB 52596 Vorstand: Robert Peters, Aufsichtsrat: Christian Hecht (Vorsitz)

4 5

standalone vs GUI character parsing
by Bridger Dyson-Smith 13 Jun '17

13 Jun '17

Hi all - I'm able to create a database with the GUI from an XML document that contains an invalid character (U+0000) -- I guess BaseX does some character scrubbing, which is awesome :). When I try creating a database with the same input XML document from the commandline (using the basex executable), I get an error message. Here are my commands in standalone mode: BaseX 8.5.3 [Standalone] Try 'help' to get more information. > create db test-bad-char /usr/home/bridger/src/another-test.xml "/usr/home/bridger/src/another-test.xml" (Line 4): An invalid XML character (Unicode: 0xb) was found in the element content of the document. > xquery db:create("test-bad-char", "/usr/home/bridger/src/another-test.xml", "/usr/home/bridger/src/", map { "chop": false() }) Stopped at ., 1/10: [FODC0002] "/usr/home/bridger/src/another-test.xml" (Line 4): An invalid XML character (Unicode: 0xb) was found in the element content of the document. > This isn't a surprise (I'm more surprised (pleasantly) by the GUI behavior); is there a way to apply the same "scrubbing" from the GUI in standalone mode? I'm sure there is, but I'm not able to figure out which option to apply. As always, thank you for your time and trouble, and thanks for BaseX. Best, Bridger

3 17

Configuring basexgui - keeping directory context
by Bridger Dyson-Smith 15 May '17

15 May '17

Hi all -- apologies for the strange title: I'm not quite sure how to word my question. I'm having a problem with maintaining the correct context of basexgui, particularly with testing some .bxs files. I have a directory where I've been keeping my BaseX installs: /usr/home/bridger/src/basex = $baseXhome. I've been in the habit of starting new tests and projects in the repo directory in $baseXhome; e.g. $baseXhome/repo/new-test. In the new-test directory, I have the following: new-test/ data/ resources/ add.xq .basex .basexgui .basexhome check.bxs add.bxs check.bxs is a simple script: CHECK foo RUN add.bxs CLOSE add.bxs runs an xquery script: RUN resources/add.xq and the `add.xq` is (surprisingly) another simple script: let $msg := file:current-dir() return $msg The problem I'm having is that, unless I `cd ~/src/basex/repo/new-test && basexgui`, `basexgui` isn't able to determine the relative file path(s) of any of the secondary scripts (add.bxs and resources/add.xq). While it wouldn't be a terrible burden to launch the GUI from a new terminal (thank heavens for multiplexers!), the problem there is that basexgui seems to default to (re)opening the last directory where it was launched; in other words 1. `cd ~/src/basex/repo/new-test && basexgui` and the GUI launches and things look great. 2. in a new terminal window: `cd ~/src/basex/repo/old-test && basexgui` and the GUI launches and opens the new-test directory. So, I guess that's two problems, but they're both somewhat related to the relative directory path context of the GUI. I've tried adding .basexhome (manually) and .basexgui (manually and letting the GUI add them automatically), but those files don't seem to help matters. Is there anything else that I can try to resolve this? I know that I can use absolute file paths, but I have a simple project that I want to share with a colleague. Is the solution to add some XQuery that will determine file paths, and add/insert that into the command .bxs files? Thanks so much for your time and trouble. Best, Bridger

2 3

BaseX scaling and real-time analytics
by Simon Wong 25 Apr '17

25 Apr '17

I'm doing a BaseX evaluation to characterize its performance with my use case. In my use case, I am receiving XML files over the network at a rate of about 100 / sec. I want to insert them into BaseX and perform real-time analytics. These XML files ranges from 20 to 50 nodes and in general has a similar strucuture. I will be periodically running XQuerys on this dataset. I am using the network API in Python to add documents in a tight loop to determine throughput. I notice that when the database is empty, adding 1000 documents takes about 1 second. When the database is loaded up with 30,000 documents, adding these 1000 documents takes about 5 seconds. I was able to get much better scaling with AUTOFLUSH off, and periodically executing a flush command. So far with a million documents in the database, adding documents seem to take close to constant time which is great. I haven't gotten to optimizing queries yet. Doing some simple aggregate queries like count(//), it looks like the query time scales linearly with the number of documents in the database. Are there any general strategies to optimizing real-time analytics use cases? Any options that can be tuned to increase document insertion and query speeds and scaling? Or perhaps indexing options that might work better for a dataset that is always changing and increasing? Thanks, - Simon

2 1

db:backups, db:ouptut order of operations.
by France Baril 21 Apr '17

21 Apr '17

Hi, What am I doing wrong? It was my impression that db:ouput was not executed until the database updates were completed. However, when I execute: let $db-name := 'Inve' return ( db:create-backup($db-name), db:output(db:backups($db-name)) ) The list of backups returned doesn't include the backup just added by db:create-backup(). I just tried with 8.6.3 to make sure it wasn't an older issue. Thanks! -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com

2 4

Re: [basex-talk] Get session config info
by Bram Vanroy 20 Apr '17

20 Apr '17

Hi Christian Do you mean a basex admin, a sys admin, or something else? Thanks Op 20 apr. 2017 13:41 schreef Christian Grün <christian.gruen(a)gmail.com>: Hi Bram, Users with admin permissions can request the database path via "db:system()//dbpath". Hope this helps, Christian On Wed, Apr 19, 2017 at 2:13 PM, Bram Vanroy <bram.vanroy1(a)student.kuleuven.be> wrote: > Hi List > > > > In a .basex file we can set the destination of our database. If we then > create a server, and create a database using a client, the BaseX-files will > be created in that directory. Is it possible to get the path to this > directory from within the client? In Perl I tried running the following > command after looking through the basex client, but I got an ‘undef’: > > > > my $session = Session->new($host, $port, $user, $pw); > > my $t = $session->info; > > $session->close; > > > > print $t; > > > > Any ideas how to get the configuration values for a basex server from a > (Perl) client? > > > > Thank you > > > > > > Bram > >

2 1

Get session config info
by Bram Vanroy 20 Apr '17

20 Apr '17

Hi List In a .basex file we can set the destination of our database. If we then create a server, and create a database using a client, the BaseX-files will be created in that directory. Is it possible to get the path to this directory from within the client? In Perl I tried running the following command after looking through the basex client, but I got an 'undef': my $session = Session->new($host, $port, $user, $pw); my $t = $session->info; $session->close; print $t; Any ideas how to get the configuration values for a basex server from a (Perl) client? Thank you Bram

2 1

Re: [basex-talk] xquery:eval error propagation
by Iwan Briquemont 18 Apr '17

18 Apr '17

Dear Christian, Perfect! I had not seen that option yet. Thank you, Iwan Le 18 avr. 2017 12:16, "Christian Grün" <christian.gruen(a)gmail.com> a écrit : Dear Iwan, Thanks for the feature proposal. As you may have seen, the xquery:parse function provides a 'pass' option, which can be used to pass on the original error info [1]. I have now added this option to xquery:eval [2], and to all other functions that support the same options. Feedback on the latest stable snapshot is welcome [3]. Cheers, Christian [1] http://docs.basex.org/wiki/XQuery_Module#xquery:parse [2] http://docs.basex.org/wiki/XQuery_Module#xquery:eval [3] http://files.basex.org/releases/latest/ On Tue, Apr 18, 2017 at 11:28 AM, Iwan Briquemont <tracnar(a)gmail.com> wrote: > Hello, > > I use xquery:eval to evaluate some user provided queries. > > It works well but when there is an error the true origin of the error > is hidden, as it will give the file and line of the xquery:eval call. > > Is there any way to pass the origin of the error through the > xquery:eval? > I guess the best would be to keep both origins. > > My workaround is to do a try/catch inside the evaluated query and wrap > the result with the error variables. It's a bit cumbersome and does not > work for static errors. > > Thank you, > Iwan

1 0

xquery:eval error propagation
by Iwan Briquemont 18 Apr '17

18 Apr '17

Hello, I use xquery:eval to evaluate some user provided queries. It works well but when there is an error the true origin of the error is hidden, as it will give the file and line of the xquery:eval call. Is there any way to pass the origin of the error through the xquery:eval? I guess the best would be to keep both origins. My workaround is to do a try/catch inside the evaluated query and wrap the result with the error variables. It's a bit cumbersome and does not work for static errors. Thank you, Iwan

2 1

basexgui.bat doesn't start
by Ulrike Schaper - SideStep Business Solutions GmbH 18 Apr '17

18 Apr '17

Dear Christian, I just installed BaseX 8.6.3 on Windows Server 2012, but the BaseX GUI doesn't start up when I use basexgui.bat. Using the exe is fine, but I need some additional lib files, which of course won't be loaded via the exe. Is there something I overlooked? Best regards, Ulrike.

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk April 2017