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

BaseX has been updated on Filecluster.com
by FileCluster Support 12 Nov '11

12 Nov '11

Dear Developer, You have received this email because we have updated BaseX and this was the contact email for the application. Your application update status BaseX has been updated on FileCluster.com to the 7.0.2 version. You can check out your application on our site at: http://www.filecluster.com/Business-Office/Database-Management/Download-Bas… If you want to let your users know about your software page on FileCluster.com, to rate it and review it, you can also use this banner to link it: Promote your software As a software website, it`s our duty to help the developers promote their software. Fortunatelly, our software promotions are cost free, for more informations please visit our promotion page. Submit your press releases We are also accepting press releases from software developers. All you have to do is to submit your press release and we will take care of the rest. Useful developer links All the essential links you need as a developer on FileCluster.com: Link to us - download banners or text links for linking to FileCluster.com Submit your software - Submit your software via PAD or manually Submit your press release - submit your press releases using our online form Contact Us - contact our editors Promote your software - our promotions page If you do not wish to receive any further notifications or confirmations from FileCluster.com, please send us an email and request a contact removal (email removal). Keep in mind that this means you will not receive ANY contact from us, including: software promotions, update confirmations or security alerts (antivirus and spyware test results). Regards, Renta Cezar - Senior Editor FileCluster Labs www.filecluster.com

1 0

FileGuru: BaseX 7.0.2 Published Today at FileGuru
by FileGuru 12 Nov '11

12 Nov '11

Dear BaseXWe are www.fileguru.com Editors. We have published your software BaseX 7.0.2 today in our site. Watch your listing here: Location: http://fileguru.com/BaseX/info Category: Business \ Information Database Your software has been reviewed and received 5 of 5 stars award. We like to congratulate you for this great useful software. Please feel free to display the award on your website and promotional materials. We recommend you to link your software, because this link will increase your ranking in the search engine and categories. And your software should be visible on the top! So, to provide a link to FileGuru from your site, you can find nice buttons at http://www.fileguru.com/linkus You can link to your software info page http://fileguru.com/BaseX/info Sincerely yours, FileGuru Team - http://www.fileguru.com © 2000-2011, FileGuru.

1 0

BaseX 7.0.2: 11-11-11 Edition
by Christian Grün 11 Nov '11

11 Nov '11

Dear list, we have just released a new maintenance release of BaseX, which contains the following features and updates: FULL TEXT - Stemming support for Japanese text corpora (thanks to Toshio HIRAI!) STARTUP - Updated start scripts (thanks to Ralf Jung!) - System property "org.basex.path" added to specify project's home directory (thanks to malamut2!) XQUERY - Numerous minor XQuery 3.0 enhancements and fixes - Fix for db:optimize() calls (thanks to Martin Hillert!) STORAGE - Fix to retain newly introduced namespaces (thanks to Laurent Chevalier!) USERS - Default privileges for new users set to "none" (thanks to Pascal Heus!) REST - query base URI for evaluated queries is now $HTTPPATH (thanks to Florent Georges!) We recommend all of you to switch to the latest version.. Have fun, Christian BaseX Team

1 0

Re: [basex-talk] BaseX 7.0.1: Release early, release often..
by Ralf Jung 10 Nov '11

10 Nov '11

Hi again, I saw you committed this - thanks a lot :) Kind regards, Ralf On Sunday 06 November 2011 22:23:03 Dimitar Popov wrote: > Am Sonntag, 6. November 2011, 21:26:03 schrieb Ralf Jung: > > Hi, > > > > this will break if the link is absolute, since it will still prepend the > > $(dirname "$FILE") to the value we got from readlink. So if I call > > /home/r/bin/basexhttp, which is a link to > > /home/r/bin/basex/bin/basexhttp, it will set FILE to > > /home/r/bin//home/r/bin/basex/bin/basexhttp. > > Yes, I saw that, but a second after I sent the email :) > > > Also, I wonder why you are splitting $SOURCE into basename and dirname, > > just to concat it again? > > Yep, that was not necessary. Here is a version, which I hope works > correctly: > > FILE="${BASH_SOURCE[0]}" > while [ -h "$FILE" ] ; do > SOURCE="$(readlink "$FILE")" > FILE="$( cd -P "$(dirname "$FILE")" && \ > cd -P "$(dirname "$SOURCE")" && pwd )/$(basename "$SOURCE")" > done > BASEX_DIR="$( cd -P "$(dirname $FILE)" && pwd )" > > Dimitar

1 0

What's the diff between Database and collection
by Edward Fong 10 Nov '11

10 Nov '11

Hi, What's the diff between Database and collection? I think there are same in baseX, am I right? And how to query by a document name? Following are steps of my testing: 1: loaded some xml files form a directory: d:\data\org-*.xml 2: query by doc('org-100525.xml') and got File or directory "D:/Program Files (x86)/BaseX701/bin/org-100525.xml" not found message. 3: because after loaded xml, directory: d:\data\org-*.xml was removed. I can't query by doc('d:\data\org-100525.xml') Thanks, Edward

4 9

xquery update impact on server?
by Pascal Heus 09 Nov '11

09 Nov '11

All: I'm running an long "xquery delete node" on one of my database and this pretty much seem to make my server unavailable for other operations. I expect this query to run for a few hours (affecting a few million nodes, database is around 800Mb). I'm running this on a Amazon EC2 small instance (1 CPU, 1.7Gb RAM) and the CPU has been stuck at 100%. If I attempt to query any database on the server (not only the one being updated), I basically don't get anything back. So do heavy xquery update requests basically lock down the server? Anyone else having similar experience? Feedback/suggestions? best *P

4 5

Bugreport
by Hillert, Martin, le-tex 08 Nov '11

08 Nov '11

Ziel der Query ist es, nach der Manipulation der DB selbige zu optimieren. Query: let $w := (//work)[position() = 17]//impression[1] return ( if ($w/@has_archive_data) then delete node $w/@has_archive_data else (), db:optimize("index") ) Error: Potential bug? Improper use? Your feedback is welcome: Contact: basex-talk(a)mailman.uni-konstanz.de Version: BaseX 7.0.1 Java: Sun Microsystems Inc., 1.6.0_07 OS: Linux, i386 Stack Trace: java.lang.ArrayIndexOutOfBoundsException Beste Grüße, Martin Hillert -- Martin Hillert Senior Analyst Enterprise Applications le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 130, Fax +49 341 355356 530 martin.hillert(a)le-tex.de, http://www.le-tex.de Registergericht / Commercial Register: Amtsgericht Leipzig Registernummer / Registration Number: HRB 24930 Geschäftsführer: Gerrit Imsieke, Svea Jelonek, Thomas Schmidt, Dr. Reinhard Vöckler

3 3

Re: [basex-talk] BaseX 7.0.1: Release early, release often..
by Ralf Jung 07 Nov '11

07 Nov '11

Hi, > Yep, that was not necessary. Here is a version, which I hope works > correctly: That's looking great, I just added a missing " " around the last $FILE. FILE="${BASH_SOURCE[0]}" while [ -h "$FILE" ] ; do SOURCE="$(readlink "$FILE")" FILE="$( cd -P "$(dirname "$FILE")" && \ cd -P "$(dirname "$SOURCE")" && pwd )/$(basename "$SOURCE")" done BASEX_DIR="$( cd -P "$(dirname "$FILE")" && pwd )" Of course, in the remainder of the script, $PWD has to be replaced by BASEX_DIR... or, to make things slightly more readable, BASEX_DIR could be the actual dir with the main jar, not the bin dir. While I was at it, I also fixed the "list all jars in lib/" part to work properly if the path basex lives in contains a ' ' (which would previously have been replaced by a ':'). You can find the result attached. It works here, but should be tested on some different setups :D Kind regards, Ralf

1 0

Re: [basex-talk] very common attribute values/custom indexing
by Christian Grün 07 Nov '11

07 Nov '11

Ross, > The DSI Utilities (http://dsiutils.dsi.unimi.it/) are a very> interesting set of classes. Thanks; I'll soon have a look at that package. Just some quick feedback, regarding the extension of index entries: we'd get even better results by extending the index entries with id's to the unique location paths.. e.g.: <a> <b>dig</b> <c>dig</c> <c>diz</c> </a> Path Index: 0: a/b 1: a/c Value Index: dig.0 -> /a/b/text() dig.1 -> /a/c/text()[.='bla'] diz.1 -> /a/c/text()[.='blu'] This way, we could completely give up path inversions, at least in a number of trivial cases. In both cases, I guess that most effort has to be put into the adaptation of the query optimizer. Volunteers are welcome.. ;) Christian___________________________ On Wed, Nov 2, 2011 at 11:29 PM, Ross Judson <rossjudson(a)gmail.com> wrote: > You guys are wizards at making the JVM run fast, without a doubt. I > haven't looked to see how namespaces are handled right now, within the > indexing scheme. In my particular case I do not have namespaces, but > clearly they need to be handled, generally. > > The DSI Utilities (http://dsiutils.dsi.unimi.it/) are a very > interesting set of classes. I have previously used these to construct > indexes of RDF-type triples. They are _extremely_ high performance, > able to process at average rates of hundreds of thousands of tuples > per second. > > The ImmutableExternalPrefixMap was very useful. I created compound > strings (subject-property-object) and stored them. I could then do a > very fast lookup on any prefix, like subject, or subject-property. The > prefix map would supply the applicable interval. By creating another > index compounding (object-property-subject), I could lookup all usages > of a given property value (object), restricting by property name, or > all the way to a specific subject. > > The ImmutableExternalPrefixMap uses an in-memory structure to compute > approximate intervals on any given query; it then reads disk to refine > and answer the query. The net result is that you generally have access > to the results of any given query in one sector read (more or less > like a hash structure), but the data is _ordered_, which means you can > perform range queries, at the cost of reading additional sectors as > necessary. > > Within BaseX you have already converted tokens to byte arrays. > ImmutableExternalPrefixMap does this as well. > > A useful experiment would be to add a new type of index to BaseX that > incorporates one of these prefix maps. > > Creating the compound index looks something like this (altering > ValueBuilder.build()). Replace: > > index.index(data.text(pre, text), pre); > > with: > > byte [] attrName = data.name(pre, Data.ATTR); > int parentElement = data.parent(pre, Data.ATTR); > byte [] elementName = data.name(parentElement, Data.ELEM); > TokenBuilder tb = new TokenBuilder(data.text(pre, text)); > tb.add(';'); > tb.add(attrName); > tb.add(';'); > tb.add(elementName); > index.index(tb.finish(), pre); > > Not sure if I have all of that right, but it shows the idea. When I > run with this the indexes on my data do expand a little, but not too > much (may a 10% growth?). Of course, it will be different for > everyone, depending on their content. > > By checking the database properties you can see that the index has > more keys in it. Next step would be to add a prefix-scanning mode to > the index iteration, in addition to equality scanning. In the example > above I use the ';' character to separate the composite token; (byte)0 > might be more appropriate.

2 1

Error: "xbug80.dtd" could not be parsed.
by Florent Georges 06 Nov '11

06 Nov '11

Hi, When using the BaseX-7.0.2pre-20111030 GUI, and try to create a new database, I fill in the form with the name and location, then press OK. Some files seem to be created, then after a few seconds I get the following error: "TestInputs/bug/bug80.xml" (Line 3): "xbug80.dtd" could not be parsed. I don't know what it means in this context. Any idea? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/

2 7