BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5250 discussions

db:replace and error bxerr:BXDB0007 (opened by another process)
by James Ball 21 May '15

21 May '15

Hello, I’m currently writing a small RESTXQ application that receives POSTed XML and then stores it into the database. It works well but I want to make it more robust so I’m adding more error handling code. One scenario I want to cover is where the database to be written to exists but is open in another process for some reason. In my function I do something like this: try { db:replace(“DATABASE_NAME”,”PATH/TO/FILE”,<Element/>) } catch * { db:output(<insert code here>) } I expect that this code should complete without error - knowing of course that the database won’t be updated. Instead I always get a bxerr:BXDB0007 error thrown and I can’t find any way to catch it. (It’s also not listed as a possible error in the documentation, although is against db:create) Is this something subtle to do with the pending updates list? I’m sure I’m missing something obvious but I can’t see it. Thank you for any help and direction, James

2 4

BaseX 8.2: The Summer Edition
by Christian Grün 21 May '15

21 May '15

Dear all, We invite you to check out Version 8.2, the Summer Edition, of BaseX, our XML database system and XQuery 3.1 processor! You can expect the following features: XQUERY - much faster sequence modification via finger trees - improved compliance with XQuery 3.1 DBA - open, save and delete queries - better Tomcat support STORAGE - updatable index structures: reduced disk space consumption XQUERY FUNCTIONS - Standard Module: fn:json-to-xml, fn:xml-to-json - Web Module: web:encode-url, web:decode-url - File Module: file:is-absolute, file:resolve-path - Admin Module: admin:delete-logs - Database Module: db:output-cache BUG FIXES - locking, full-text requests, stemming REMOVED FEATURES - event handling (will be replaced by database triggers) The latest version is available at http://basex.org. As usual, various minor bugs and inconsistencies have been fixed in the latest version; check out our documentation (http://docs.basex.org) and the GitHub commits (https://github.com/BaseXdb/basex) for more details! We are looking forward to your feedback, Your BaseX Team

1 0

rest vs. restxq - strange difference
by Lars Johnsen 20 May '15

20 May '15

I am running a web script in two identical versions (identical as in "cut and paste"), one via RESTXQ and one vi REST. The response is different, and I wondered what may be the trouble. For example the output (the URLs only works locally) for http://ljohnsen:8984/hyphens/mellom is the same as http://ljohnsen:8984/rest?run=hyphen-show.xq&word=mellom which is a set of hyphenation data: mellom mel - lom 17005 Mel - lom 144 mel - lom. 50 but if "mellom" is exchanged with "nasjonalbiblioteket" only the REST version shows any result, which then is the same as I get experimenting in the GUI. The actual script is added below, and which runs in both versions (identical apart form the rest and restxq interfaces), it uses full text search, but results differ when run under the REST-regime. All the best Lars G Johnsen National Library of Norway module namespace page = 'http://basex.org/modules/web-page'; declare %rest:path("/hyphens/{$word}") %output:method("html") function page:show-hyphens($word) { let $db := db:open('hyphen-data') let $hyphens := for $hyp in $db/hyphens/hyphens[full contains text {$word}] group by $first := $hyp/first, $second := $hyp/second let $count := count($hyp) order by xs:int($count) descending return element p { attribute freq {$count}, $first, " - ", $second, $count } let $total := sum($hyphens//@freq) let $div := element div { element p {$word}, for $hyp in $hyphens return element div { attribute class {"hyph"}, attribute style {"font-size:", 1 +round(xs:int($hyp//@freq/data()) div $total,1) || "em"}, $hyp } } return <html encoding="UTF-8"> <head> <meta http-equiv="Content-Type" content="text/html" charset="UTF-8" /> <title>Orddelinger</title> </head> <body>{$div} </body> </html> };

2 12

Create DB from large XML extraction without root element?
by Hondros, Constantine (ELS-AMS) 19 May '15

19 May '15

Hello all, I have a huge extraction of XML documents in a single file, without a root element, something along these lines: <a> <b/> </a> <a> <b/> </a> ... Other than by editing it to add a root element, is there a clever way of creating a Basex DB from this? Thanks for any pointers, C. ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.

3 4

Server protocol bug?
by alxarch 18 May '15

18 May '15

Hi, While testing for basex-stream i encountered a weird behavior in the OPTIONS query command. After creating the query ```xquery declare option output:method "json"; declare option output:json "lax"; <json type="object"/> ``` the response of OPTIONS was: `json=lax=true,method=json` Which seems wrong. I event tried setting cdata-section-elements to "pre, code" and the response had a double comma ("cdata-section-elements=pre,,code,method=xml") Is this a bug or is there some deterministic method of parsing the response? Thanks, Alex

2 2

DB size sanity check
by Hondros, Constantine (ELS-AMS) 18 May '15

18 May '15

Hi all, Database created from 17692 MB: resulting DB size 30450 MB. CHOP is set to false, but for good reasons. TEXTINDEX and ATTRINDEX are true, but FTINDEX false. Can I just sanity check this size of DB? It surprises me a little. (Basex 8.0.2 by the way). Thanks in advance, Constantine ________________________________ Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The Netherlands, Registration No. 33156677, Registered in The Netherlands.

2 1

Bug in declare base-uri
by Hans-Juergen Rennau 18 May '15

18 May '15

Dear BaseX team, I think there is a bug in the determination of the static base URI in the special case that a base URI declaration contains a relative URI equal to or starting with "..". Consider this declaration:declare base-uri ".."; The effect should be that relative URIs are resolved against the PARENT directory of the directory containing the query. If the query is located at, say, file:///a/b/c/query.xq, I would expect the static base-uri to be /a/b/, so that a URI like "abc.xml" would be resolved to file:///a/b/abc.xml. However, the static base URI as determined by BaseX in this case misses the trailing /, it is: file:///a/bThe effect is that a URI like "abc.xml" would be resolved to file:///a/abc.xmlIn other words: URIs are resolved against the "GRAND-PARENT" directory of the query. Final remark: the effect of resolving URIs against the parent directory of the query is achieved by the surprising base URI declaration: declare base-uri "."; which is not what I would expect. Conclusion: the way to achieve a resolving of relative URIs against the parent directory of the query should be achieved by the base URI declaration ".." - and no other value. Kind regards,Hans-Juergen Full example:Query ( file file:///projects/infospace/pcol/test.xq); declare base-uri ".."; declare variable $uri external; string-join(( 'query-file: file:///projects/infospace/pcol/test.xq', concat('static-base-uri: ', static-base-uri()), concat('resolve-uri("try.xml")=', resolve-uri("try.xml")) ), '
') Output:query-file: file:///projects/infospace/pcol/test.xq static-base-uri: file:///C:/projects/infospace resolve-uri("try.xml")=file:/C:/projects/try.xml

2 4

Open database outside DBPATH
by Ketill Fenne 18 May '15

18 May '15

Hi! Maybe this has been answered before, but is it possible to open and read a database located outside DBPATH? Kind regards Ketill Fenne

3 4

java.lang.NullPointerException while monitoring events
by alxarch 18 May '15

18 May '15

Hi again, I have stumbled upon a null pointer exception in the event monitoring protocol The behaviour is inconsistent, some times the tests pass and some they stumble upon this error. It seems to be triggered right after I execute a query that triggers an event `db:event('TESTEVENT', "12345")` The server version is the 8.1.1 Thanks, Alex

2 1

New BaseX client for nodejs
by alxarch 17 May '15

17 May '15

Hi all, I am making a new BaseX client for nodejs. It focuses on utilising node streams in order to be able to pipe data to/from BaseX directly. (i.e. pipe request body to an ADD command or pipe XQuery output to a response). It also uses promises for more code flow flexibility. Features: - Supports streams where appropriate (command output, query execution, add, store etx) - Promises interface I plan to release it in NPM within the week (It lacks proper documentation and I want to organise my tests as mocha tests). Alex

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk