May 2015 - BaseX-Talk - mailman.uni-konstanz.de

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

Separate Databases vs. Directories Within One Databse?
by Eliot Kimber 16 May '15

16 May '15

In the discussion of adding metadata to a bunch of files Christian points out that you can both limit queries to directories within a single database or apply a query to multiple databases. My question: when or why would you prefer one approach over the other? In my case I'm using BaseX to reflect the XML contents of git repositories. My current approach is to create a separate database for each repo/branch pair, my reasoning being that that makes it easiest to limit queries to just that branch. Because the BaseX data is intended to be a read-only reflecting of the git-managed source, it also makes it easy to clear the data for a branch if it's gotten out of sync (or I suspect it's gotten out of sync) by simply dropping the database. I have complete control over the queries (through a library of functions that understand the git nature of the databases), so I could just as easily use a single database with subdirectories that reflect the repos and branches. In this scenario, as an example, is there any compelling reason to use one approach or the other? I like having one database per branch because that seems like a natural mapping that generally keeps things simple and more or less obvious (e.g., doing "list" will show the list of databases, which reflect the repo and branch names in their names). In this application the scale will usually be relatively small: 1000s or 10s of 1000s of individual documents in any given branch but the querying and indexing, which supports maintaining knowledge of the links within the XML content, could get intense. Cheers, Eliot ————— Eliot Kimber, Owner Contrext, LLC http://contrext.com

2 2

BaseX native User module
by Marco Lettere 16 May '15

16 May '15

Hi Christian, do you have any idea on the performances of the users module that comes with BaseX? Does it work properly with a count of users up to several hundreds? thousands? Any tests done so far? Thank you. BR, Marco.

2 1

Lock/release question
by France Baril 14 May '15

14 May '15

Hi, I am trying to find documentation on functions to explicitly lock/unlock specific files stored in BaseX for a predefined user. Something like: db:lock('db, 'file.xml', 'user', 'write') Something like: db:get-lock-details('db', 'file.xml') would be interesting too. I couldn't find anything. Am I supposed to work with the ~webdav DB? We're trying to get away from the WebDAV interface. Thanks, France -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com

2 3

BaseX Java examples
by Menashè Eliezer 14 May '15

14 May '15

Hello, The page http://docs.basex.org/wiki/Java_Examples is very detailed. However, I wonder in which cases one should use the BaseX XQJ API and not the standard client. e.g., which client offers a better performance? -- With kind regards, Menashè

2 1

Joe Wicentowski collects sites that are powered by XQuery
by Alexander Holupirek 13 May '15

13 May '15

For those who have sites that are powered by BaseX/XQuery. > Begin forwarded message: > > From: Joe Wicentowski <joewiz(a)gmail.com> > Subject: [xquery-talk] @XQuery, #xquerypower, and related efforts > Date: 13. Mai 2015 21:03:56 MESZ > To: XQuery Talk <talk(a)x-query.com> > > Dear XQuery Talk, > > Friends of Jim Fuller may know that, after many years of excellent stewardship, Jim decided to give up his @xquery twitter account for @_jim_fuller. I've taken on the task of using the account to post links of interest to users and learners of XQuery, and promoting the use of XQuery. > > https://twitter.com/XQuery <https://twitter.com/XQuery> > > I'm currently posting a daily link to sites that are powered by XQuery. I've begun collecting these in a simple GitHub page. I would welcome all to submit pull requests. > > https://github.com/joewiz/xquerypower <https://github.com/joewiz/xquerypower> > > And I'd encourage anyone interested to follow @XQuery. I'll gladly retweet items of interest, and the easiest way for me to notice you is to use the term "XQuery"! > > Thanks, > Joe > _______________________________________________ > talk(a)x-query.com > http://x-query.com/mailman/listinfo/talk

1 0

unexpected behaviour
by Rob Stapper 13 May '15

13 May '15

Hi Christian, Can you have a look at the attached program. Both items of the returned sequence of the program should do the same thing. Both do give the same, correct result: an empty sequence, but the first item unnecessarely triggers function: "local:f1#1" , while the second item doesn't. This a pity since "local:f1#1" could be a time-consuming function. Cheers, Rob --- Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. http://www.avast.com

3 2