BaseX-Talk January 2017

basex-talk@mailman.uni-konstanz.de

30 participants
33 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

Tail Recursion Error on startup
by buddyonweb-software＠yahoo.com 11 Mar '17

11 Mar '17

When we start up BaseX (whether the server or the GUI) and run a particular a query against a particular .xqm file, we always get a tail recursion error. Error:[bxerr:BASX0005] Stack Overflow: Try tail recursion? If we attempt to execute it again (sometimes twice, but have done so repeatedly up to 5 times), the error goes away and all is fine. Is there anything you can suggest or anything we can provide you to see how to eliminate this. This is particularly problematic on our server when we reboot our production application.Anything you can suggest or anyway we can help is much appreciated. Buddy

3 7

Re: [basex-talk] Send multipart binary with http client
by Christian Grün 09 Feb '17

09 Feb '17

Hi Max, Do you have an MCVE for us? Thanks in advance, Christian Am 30.01.2017 4:24 nachm. schrieb "Maximilian Gärber" <mgaerber(a)arcor.de>: Hi, this seems related to https://github.com/BaseXdb/basex/issues/1203 Problem 1: When setting Content-Transfer-Encoding manually (via <http:header>), it will appear twice in the request that is sent Problem 2: I cannot override base64 because it happens automatically based on the content I am sending and for some reason the web server that receives this request does not recognize the base64 encoding correctly Regards, Max 2017-01-30 15:35 GMT+01:00 Maximilian Gärber <mgaerber(a)arcor.de>: > Hi, > > I can't figure out how to send a file in binary (not base64) when > using multipart [1] > > On the body, I've tried method="basex" because the docs says this > would write raw bytes to the request > > Regards, > Max > > > [1] > > declare function _:send-multipart($url, $file-name, $path) as item()* { > > > let $uri := file:path-to-uri($path || $file-name) > let $type := fetch:content-type($uri) > > let $binary := file:read-binary($path || $file-name) > let $boundary_id := concat("batch_", random:uuid()) > > let $req := > <http:request method="post" send-authorization="false" > override-media-type="text/plain"> > > <http:header name="Accept" value="application/json"/> > <http:header name="Accept-Encoding" value="gzip, deflate"/> > > <http:multipart media-type="multipart/form-data" > boundary="{$boundary_id}"> > > <http:header name="Content-Transfer-Encoding" value="binary"/> > <http:header name="Content-Disposition" value="form-data; > name='FILE'; filename='{$file-name}'"/> > <http:header name="Content-Type" value="{$type}"/> > >  > <http:body media-type="application/octet-stream" method="binary"> > {$binary} > </http:body> > > </http:multipart> > </http:request> > > let $resp := http:send-request($req, $url) > return json:parse($resp[2]) > > };

2 5

Upload XML File to Remote Basex Server with database module
by Detlef 06 Feb '17

06 Feb '17

Good Afternoon, I'm developing an interface, written in Delphi 10.1 Berlin, to a remote Basex Server, using HTTP-Server For uploading, I use the db:add query. The problem is, that I cannot upload a file, which is stored on a local path of my computer. If this file is stored on a network resource, uploading is not a problem. If I transfer the file content into a string and send this string via the above query, I got error 413 (Request entity too large) How can I solve this problem. Best regards Detlef Schmitz

2 4

XQuery performance degradation as number of json files grows
by Baysdon, Joseph 31 Jan '17

31 Jan '17

The performance of XQuery updates degrades as the number of JSON resources in my BaseX instance grows. In what ways might the number of JSON resources affect the performance of an XQuery update for a particular XML resource? I was under the impression that JSON resource were not indexed. (Note: this particular performance degradation is most dramatic when the BaseX server points to an NFS mount for the BaseX database.) Thanks, Joe

2 3

Is it possible to use indices in sub-queries
by Clemens Müthing 31 Jan '17

31 Jan '17

Hello everyone I’ve recently started to use and stumbled upon a problem with the indices in basex that I do not fully understand and was hoping for some clarification. So basically I’ve got a bunch of xml files in my database with medical ICD-10 codes that all look like this: <classification name=„some-name“ year=„2017“ > <code> <value>03R80JZ</value> <final>true</final> </code> <code> <value>2W3JX1Z</value> <final>false</final> </code> … ... </classification> The db can contain multiple of these files, one for each name and year, and each classification can contain up to 100k of those codes (all values are unique). What I’d like to do now is, given a list of codes, check if those codes actually exist in the classification for a given name and source. So I came up with this straight-forward piece of code: let $proc := ('F0723EZ','0JWS37Z','0W054JZ','0NQ00ZZ','03R80JZ','0PW537Z','0RW940Z','0PPD0KZ','2W3JX1Z','0D9B8ZZ','0SWC30Z','0PRJ4KZ','025R0ZZ','0T1347C','0S950ZX','008J4ZZ','0D110K4','0XUV4JZ','0GTN4ZZ','4A133J1’) for $p in $proc return /classification[@name=‚some-name‘ and @year=2017]/code[value = $p] This does work fine, however it takes roughly one second to evaluate the query, and in the Query Info Window I can see that the text index of the db is not being used. However I do see that the attribute index is being queried. Now I noticed that, if I drop the attribute index, the query is evaluated basically instantaneous and can see that the query is rewritten to use the text index as well. So my question is: Is this normal, i.e. is it not possible to use multiple indices in one query at once? Or is this a problem where the „sub-query“ …./code[value = $p] is only evaluated on the result of the first query, thus the text index is not being considered? If so, is there a way (without rewriting the whole query) to make basex use both indices when compiling the query? Thanks a lot already and all the best Clemens Müthing

2 4

Send multipart binary with http client
by Maximilian Gärber 30 Jan '17

30 Jan '17

Hi, I can't figure out how to send a file in binary (not base64) when using multipart [1] On the body, I've tried method="basex" because the docs says this would write raw bytes to the request Regards, Max [1] declare function _:send-multipart($url, $file-name, $path) as item()* { let $uri := file:path-to-uri($path || $file-name) let $type := fetch:content-type($uri) let $binary := file:read-binary($path || $file-name) let $boundary_id := concat("batch_", random:uuid()) let $req := <http:request method="post" send-authorization="false" override-media-type="text/plain"> <http:header name="Accept" value="application/json"/> <http:header name="Accept-Encoding" value="gzip, deflate"/> <http:multipart media-type="multipart/form-data" boundary="{$boundary_id}"> <http:header name="Content-Transfer-Encoding" value="binary"/> <http:header name="Content-Disposition" value="form-data; name='FILE'; filename='{$file-name}'"/> <http:header name="Content-Type" value="{$type}"/>  <http:body media-type="application/octet-stream" method="binary"> {$binary} </http:body> </http:multipart> </http:request> let $resp := http:send-request($req, $url) return json:parse($resp[2]) };

1 1

Whitespace
by meumapple 30 Jan '17

30 Jan '17

Hi, I have a problem with whitespace handling of the default BaseX XML parser. If I have: <s>and <a>this</a> is</s> the parser deletes the spaces after "and" and before "is". Why not preserving the space as default option here? This kind of space is very important. I know that with adding xml:space I can solve the problem, but this is not easy to do automatically (moreover I cannot do this with copy/modify because all spaces are deleted after adding xm:space ). Is there a parameter which forces the parser to keep the spaces, without modifying the file? And in general, can the behavior of the parser be changed?

3 3

BaseX 8.6: The Winter Edition
by Christian Grün 30 Jan '17

30 Jan '17

Dear all, BaseX 8.6 is out! The new version of our XML database system and XQuery 3.1 processor includes countless improvements and optimizations. Many of them have been triggered by your valuable feedback, many others are the result of BaseX used in productive and commercial environments. The most prominent new features are: LOCKING - jobs without database access will never be locked - read transactions are now favored (adjustable via FAIRLOCK) RESTXQ - file monitoring was improved (adjustable via PARSERESTXQ) - authentication was reintroduced (no passwords anymore in web.xml) - id session attributes will show up in log data DBA - always accessible, even if job queue is full - pagination of table results INDEXING - path index improved: distinct values storage for numeric types XQUERY - aligned with latest version of XQuery 3.1 - updated functions: map:find, map:merge, fn:sort, array:sort, ... - enhancements in User, Process, Jobs, REST and Database Module CSV DATA - improved import/export compatibility with Excel data Visit http://basex.org to find the latest release, and check out http://docs.basex.org/ to get more information. As always, we are looking forward to your feedback. Enjoy! Christian BaseX Team

5 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk January 2017