BaseX-Talk July 2014

basex-talk@mailman.uni-konstanz.de

24 participants
38 discussions

What is the best way to implement an async REST method?
by Marc van Grootel 16 Dec '14

16 Dec '14

How would you implement an async REST pattern? I don't remember having seen anything that makes me do this using plain XQuery. Does this mean the only way to tackle this would be via Java and events maybe? I would post to a URL, this URL would accept the post and return a temporary URL where I can check the status of my request, then once it's ready this temp URL will redirect me to the location of the real resource. That's the gist of the async REST pattern that I would like to implement. What would be the best approach to experiment with this? --Marc

5 9

REST queries: "Read permissions needed"
by Jérôme Chauveau 25 Nov '14

25 Nov '14

Hi, i am using BaseX79 as a webapp - embedded in a tomcat7 server. I am working on a php application which runs REST xqueries to my BaseX server. I created a "mydb" database and a user "myuser". Then i granted READ permissions for "myuser". > *GRANT read TO myuser* > *GRAND read TO myuser ON mydb* > *show users* Username Read Write Create Admin ------------------------------------ admin X X X X myuser X > *show users on mydb* Username Read Write --------------------- myuser X All my REST xqueries returns a "READ permission needed." message with the user "myuser" when its works properly with the admin user account. Moreover, REST xqueries via a web browser (logged as 'myuser') works properly too. Did i miss something? Thank's for help. Jérôme. -- Jérôme Chauveau - SAIC-CERTIC - Campus 4 Université de Caen Basse-Normandie

2 8

Full text score with or
by Andy Bunce 23 Nov '14

23 Nov '14

Hi, I want to score searches with multiple conditions e.g. let $data:=( <r><a>red apple</a></r>, <r><a>blue lagoon</a></r>, <r><b>fish and chips</b></r>) for $hit score $s in $data[ a contains text("red") or b contains text("fish")] return $s In 7.8.2 it always returns scores of zero. In version 7.6 it returns numbers like 0.6201145069582775 0.4528324252639413 Is this bug? Regards /Andy

2 3

stream binary responses from http:module
by Johan Mörén 10 Nov '14

10 Nov '14

Hi I have built a small client in XQuery that fetches zip files from another remote service using the http-module and stores them on disk with the help of the file-module. Some of the returned zip files are really large and BaseX seems to need to materialize the files in memory before writing them to disk resulting in out of memory errors for some files. Is there some way read the response in a more streamable fashion when using the http-module? I tried using the fetch:binary function successfully but i really need the more extended functionality of the http-module. #results in out of memory if the zip file is too large file:write-binary("file.zip", http:sendrequest(...)[2]) #works all the time. file:write-binary("file.zip", fetch:binary(...)) Regards, Johan

3 7

basex 7.9 - red hat package?
by Olivier JEULIN 10 Sep '14

10 Sep '14

Hello, when do you plan to release a package for RedHat? The repository has only v7.8. FYI, 7.9 solves a bug that we just found in 7.8, so, good work! :-)

4 7

serialisation before xslt
by Marc 07 Aug '14

07 Aug '14

Hi, I want to transform with xslt before to output the file. If I do a serialize on the disk, runs the xslt with saxon et write the result the space are conserved (I use chop=false to load the file in the base). But if I transform the file in BaseX, and serialize the file after, the element are passed to the xslt indented and I lost the space at the begining and the end of element. And other thing, if I put the "declare option db:chop 'false';" at the beginning of the XQuery, the file is indented, if I put it out (it's unuseful) the serialisation without indentation is done. I use the 7.9 version.

2 3

Unit module sometimes drives me nuts
by Marc van Grootel 07 Aug '14

07 Aug '14

Really, I want to be good and write my tests together with the code. I still don't do it often enough but I know it's important and for the code I'm currently working on I try to cover most of it with tests. I regret that I'm not able to get down into the guts of the Java code and help fix it, so, instead I moan ;-) No, seriously, here are a few more general things that bug me about the Unit module. - assertions causing an NPE when an XQuery error is raised but no traceback that tells me what/where the error actually is. [ex1] - assertions causing a failure/error reported, produce a test result but stop running further tests after the one that raises the error [ex2] I tried to reduce these issues into a short example but I think that they highlight a more general issue with the current Unit module. It's mainly the fact that there's no indication of the problem that forces me to add unit:ignore to all tests and one by one removing it, or executing the assertion xquery in a client to find out where the issue lies. I also have an improvement idea: - Personally, I run the tests often (minutes rather than hours), and from the shell. The XML format feedback isn't very helpful. It would be for automated test reports but I think the usability (readability) of the feedback during development is just as, if not more, important. Maybe adding an extra switch (-t for textual feedback and -tx for XML feedback) could help. It should just focus on summarizing clearly the expected, return values, failures and errors, and provide helpful context. Note that I always run the code using `basex -t` from bash and I'm running 8.0 beta 7ba9510 Note too that most of these things happen to me when doing map related stuff. ... and now I stop moaning and get back to coding. --Marc [ex1] example of test that causes an NPE without any helpful output *declare* *%unit:test* *function* *test:npe*() { *unit:assert-equals*(*map* {}('x'), *map* { 'x': 1 }('x')) }; [ex2] example of test that causes further tests to be executed *declare* *%unit:test* *function* *test:fail*() { *unit:assert-equals*(*map* {}, *map* { 'x': 1 }) }; doing map {} = map {'x': 1} causes this error [XPTY0004] map(*) and map(*) cannot be compared.

2 4

UPDINDEX and ever growing index size
by James Ball 04 Aug '14

04 Aug '14

Hello, I’ve finally had some time to look at an issue I’ve been having with databases that have UPDINDEX set to true. I’m now running a BaseX 8.0 beta and was on 7.X when I first encountered this. The issue I’m seeing is that the size of the index grows by approximately 1MB with every updating ‘transaction’ (snapshot?) even if there is no new data for the index. For example if I have a database with 100,000 files and I replace one of those files (with itself so there’s no new data) then the size of the index will go up by around 1MB. If I replace 1000 files in the same transaction (again with themselves) the size of the index will go up again by around 1MB. Dropping and recreating the index returns it to its original size. I have a current project where I’m expecting thousands of files a few at time that need to be added/replaced - I completely ran out of disk space before I spotted what was happening when testing. Is this expected behaviour? I don’t know the format for the index files but I’ve looked at atvl.basex just in a text editor. It looks like for each update to the index around 40k blank lines are being added. I don’t know that they are truly blank lines - but that’s how they’re rendering in the editor. I’ve created a small test case to replicate what I’m seeing. [Mac OS 10.9.4, BaseX 8.0 beta 496c381] Thank you for your help. Regards, James 1) SET UPDINDEX TRUE 2) CREATE DB Index-Test-Updindex-XQ 3) Run an XQuery to populate a reasonable database (I do 10,000 items) ------------------------ let $files_from := 1 let $files := 10000 let $xml := <XmlBody DocumentType="Test" DocumentCode="" TimeStamp="2014-07-14T10:57:34."> <DocumentInfo> <Name Code="54321" Value="Name"/> </DocumentInfo> <DataItems> <DataItem Code="12345" Value="Data"/> </DataItems> </XmlBody> for $i in ($files_from to ($files_from + $files -1)) let $d := copy $c := $xml modify ( replace value of node $c/@DocumentCode with $i, replace value of node $c/@TimeStamp with $c/@TimeStamp||$i, replace value of node $c/DocumentInfo/Name/@Code with $c/DocumentInfo/Name/@Code||$i ) return $c return db:replace('Index-Test-Updindex-XQ','Test/'||$i,$d) ------------------------ 4) Check the size of the index - should be about 325kB 5) Run the XQuery again (it will replace files with identical copies) but for just one file: ------------------------ let $files_from := 1 let $files := 1 let $xml := <XmlBody DocumentType="Test" DocumentCode="" TimeStamp="2014-07-14T10:57:34."> <DocumentInfo> <Name Code="54321" Value="Name"/> </DocumentInfo> <DataItems> <DataItem Code="12345" Value="Data"/> </DataItems> </XmlBody> for $i in ($files_from to ($files_from + $files -1)) let $d := copy $c := $xml modify ( replace value of node $c/@DocumentCode with $i, replace value of node $c/@TimeStamp with $c/@TimeStamp||$i, replace value of node $c/DocumentInfo/Name/@Code with $c/DocumentInfo/Name/@Code||$i ) return $c return db:replace('Index-Test-Updindex-XQ','Test/'||$i,$d) ------------------------ 6) Check the size of the index - it will be about 1MB 7) Run the XQuery again for around 100 files ------------------------ let $files_from := 1 let $files := 100 let $xml := <XmlBody DocumentType="Test" DocumentCode="" TimeStamp="2014-07-14T10:57:34."> <DocumentInfo> <Name Code="54321" Value="Name"/> </DocumentInfo> <DataItems> <DataItem Code="12345" Value="Data"/> </DataItems> </XmlBody> for $i in ($files_from to ($files_from + $files -1)) let $d := copy $c := $xml modify ( replace value of node $c/@DocumentCode with $i, replace value of node $c/@TimeStamp with $c/@TimeStamp||$i, replace value of node $c/DocumentInfo/Name/@Code with $c/DocumentInfo/Name/@Code||$i ) return $c return db:replace('Index-Test-Updindex-XQ','Test/'||$i,$d) ------------------------ 8) Check the size of the index - it will be about 2MB. 9) Drop the index and recreate it. It will be about 325kB again. --------------------------------- James Ball me(a)jamesball.co.uk

2 11

Copy between databases
by Marco Lettere 04 Aug '14

04 Aug '14

3 3

Re: [basex-talk] XML-Validation return value
by Martin Hartmann 30 Jul '14

30 Jul '14

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk July 2014