June 2011 - BaseX-Talk - mailman.uni-konstanz.de

Command line on OS X
by Craig Girard 23 Jun '11

23 Jun '11

I have 2 db's I would like to join. I have the xq thanks to help from Michael yesterday, but my db's are large and I receive a 'out of main memory' error. I have found some info on command line options but have been unable to get them to work. I am running BaseX on OS X. Is there a way to run an xq from the terminal or have the output from the xq go to a file rather than the screen? Thank you all for your help, Craig Girard

3 2

Rebind the variables
by Oda 23 Jun '11

23 Jun '11

Hi, I want to rebind the variables, but got the result that wasn't expected. How can I get the expected result without creating new processor instance? (When I use proc.query() and don't declare $var2 then got the expected result. But I have to declare $var2.) ---------- String query = "declare variable $var1 as xs:string external; " + "declare variable $var2 as xs:string := 'BBB'; " + "($var1, $var2)"; QueryProcessor proc = new QueryProcessor(query, new Context()); // "AAA BBB" proc.bind("var1", "AAA"); System.out.println(proc.execute()); //duplicate definition error of $var2 //proc.query(query); // "AAA BBB" not "CCC BBB" proc.bind("var1", "CCC"); System.out.println(proc.execute()); proc.close(); ---------- Thanks, Oda.

2 2

NEWBIE question - Joining db's
by Craig Girard 22 Jun '11

22 Jun '11

Is there a way in basex to join 2 databases together? I have 2 databases I would like to join based on an ID. I have found examples in xquery but they don't seem to work in basex. Thank you for your time, Craig

2 1

compound documents
by Imsieke, Gerrit, le-tex 22 Jun '11

22 Jun '11

What would be your recommendation for dealing with compound documents? Suppose we have a larger work of literature that consists of chapters, and for some reason we want to store the chapters as different files. A rationale for splitting the work might be that different persons should be able to edit two chapters at the same time. There’s a skeleton document that slurps in the individual chapters, maybe using XInclude or another linking/transclusion mechanism. Suppose there’s an XML database that stores a copy of the complete work and keeps it up to date. And that’s the point: how to implement the update procedure? a) Resolve transclusions first, then store whole work as one XML (as a consequence, every node has the same base URI) b) Store skeleton and individual chapter files, provide virtual single-tree view transparently (but each node would still know its base URI) c) Store skeleton and individual chapter files, leave it to the user (= xquery programmer) to create a custom transcluder for creating intermediate compound document instances that may then be queried or exported In cases b) and c), if a content unit (chapter) was edited, I’d just delete the corresponding DB item and add the changed file to the DB. In case a), I’d either reassemble the compound work and replace the probably large XML file in the DB with a new one (probably an expensive operation), or I’d replace the corresponding content via XQUF (requires that I’m able to precisely locate where the altered snippet was in the compound document). So if fine-granular file-based storage was a requirement, what would you do in order to index the content in BaseX? I think b) is desirable, but not implemented. Maybe you even know a method d)? Gerrit

1 0

whitespace pruning while storing an XML doc to BaseX, how to disable
by software developer 21 Jun '11

21 Jun '11

Hi, Does BaseX attempt some whitespace pruning on the XMLs being stored; if yes, how to get BaseX not to do so. On the wire, at the time request reaches BaseX, the XML is like: ..<xsl:for-each select="LINK"> ...<xsl:if test="A = 'TOKEN'"> ....insert into ....MYTABLE(VERSION) ....values ('LATEST'); ...</xsl:if> . in above is a space character, note the terminating xsl:if is on a line of its own. What BaseX stores is: <xsl:for-each select="LINK"> <xsl:if test="A = 'TOKEN'">insert into MYTABLE(VERSION) values ('LATEST');</xsl:if> </xsl:for-each> As you can see, BaseX has not persisted/stored the incoming XML as-is. I do not want this intelligent pruning since it breaks stuff for me. Thanks.

2 2

BaseX and integration into <oXygen/> - which edition is needed
by Jan Vlčinský (CAD) 20 Jun '11

20 Jun '11

Hi I am considering purchase of <oXygen/> and wonder, which edition is supporting integration with BaseX: It has to be Editor and not Author (Editor cares about transformations, Author about creation of content). But do I need Enterprise or I will live happily with Professional? My feeling is that Professional will be sufficient, as http://docs.basex.org/wiki/Integrating_oXygen describes general method, not bound to some specific vendor, but I can be wrong. Thanks for any reaction. Jan *Ing. Jan Vlčinský* CAD programy Slunečnicová 338/3, 734 01 Karviná Ráj, Czech Republic tel: +420-597 602 024; mob: +420-608 979 040 skype: janvlcinsky; GoogleTalk: jan.vlcinsky(a)gmail.com http://cz.linkedin.com/in/vlcinsky

3 2

Please confirm subscription to Clinical Trials Centre's newsletter! (Action required)
by magnifier 19 Jun '11

19 Jun '11

1 0

Newbie question
by Craig Girard 15 Jun '11

15 Jun '11

I am receiving the following error... No sequence (attribute SCORE [ "16" }, attribute SCORE { "16" }) allowed. Seems like a basic one but I cannot find information about it anywhere. Any suggestion are greatly appreciated. Thank you, Craig Girard

3 2

Re: [basex-talk] "database locked" error on DROP DATABASE
by Andreas Weiler 11 Jun '11

11 Jun '11

Forward to mailing-list... Begin forwarded message: > From: Andreas Weiler <andreas.weiler(a)uni-konstanz.de> > Date: 8. Juni 2011 09:54:23 MESZ > To: Godmar Back <godmar(a)gmail.com> > Subject: Re: [basex-talk] "database locked" error on DROP DATABASE > > Hi, > It seems that the database isnt closed correctly in your Session. > If you try to delete the database then with another Session, it fails, cause the first Session has it still open. > > On 08.06.2011, at 01:32, Godmar Back wrote: > >> On Tue, Jun 7, 2011 at 6:11 PM, Godmar Back <godmar(a)gmail.com> wrote: >>> Hi, >>> >>> I'm trying to delete an XML document by invoking 'execute("DROP >>> DATABASE name")' using the Java binding, but I'm getting: >>> >>> Tue Jun 07 18:06:10 EDT 2011: Unexpected exception: >>> java.io.IOException: Database 'feed_vsony7_at_vt_dot_edu_vijayfeed' is >>> currently locked. >>> java.io.IOException: Database 'feed_vsony7_at_vt_dot_edu_vijayfeed' is >>> currently locked. >>> at org.libx.libappdatabase.BaseXSessionSupport.execute(BaseXSessionSupport.java:71) >>> >>> There are no concurrent accesses to the database. I'm creating a >>> document, then I'm successfully running a few XUpdate/XQuery's on it, >>> then I attempt to delete it as part of a unit test. >>> >> >> FWIW, the problem persists in 6.6.2. >> When the DROP DB fails, show databases shows: >>> show databases >> 1 opened database(s): >> - libx2_feeds_test (1x) >> >> Here's a log: http://top.cs.vt.edu/~gback/bx/b662bugs/2011-06-07.log >> >> The documentation at >> http://docs.basex.org/wiki/Commands_6.6.3#DROP_DATABASE says "The >> command fails if the specified database does not exist or is currently >> locked, or if the database could not be deleted for some other >> reason." but nowhere else does it mention what 'locking' the database >> means. >> >> In the XQuery model, I can only see a need for locking internally >> during an XQuery, which means that leaving a database locked, or >> failing to delete it because of it (instead of waiting until it is no >> longer accessed) would be a bug. >> >>> >>> ps: >>> (I'm not issuing any "OPEN" commands. What does OPEN/CLOSE do, anyway?) >> >> Never mind about this question - this doesn't apply. >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk(a)mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >

3 13

Coming soon: database events
by Christian Grün 09 Jun '11

09 Jun '11

Dear all, we're currently working hard to get Version 6.7 of BaseX finished. One of the major new features will be the support for database events, which can be triggered and received by any client: http://docs.basex.org/wiki/Events BaseX 6.7 will offer some other features, most of which are already available in the current snapshot.. http://files.basex.org/releases/latest/ https://github.com/BaseXdb/basex Some of the new commands can be traced by comparing the old and new Command entry in our Wiki: http://docs.basex.org/wiki/Commands http://docs.basex.org/wiki/Commands_(Snapshot) If you have some early feedback, or if the current documentation does not cover all issues.. Feel free to contribute or give feedback. All the best, Christian PS: Another exciting feature we're currently implementing is the incremental update of all index structures. This feature will be available with BaseX 7.0.

2 1