BaseX-Talk June 2010

basex-talk@mailman.uni-konstanz.de

22 participants
32 discussions

ADMIN permission needed for basex:read(...)
by Sandra Maria Silcot 27 Jun '10

27 Jun '10

Fellow basex users, Test case: (as 'admin' user:) run file1.xq, containing: let $test := basex:read('/tmp/222.readme') return <test>{$test}</test> Returns, as expected: <test>readme from basex </test> But when run as any other user WITHOUT admin privilige (from the log): RUN /tmp/222 Error: ADMIN permission needed. 7.75 ms Behaviour is the same if the file is copied to be inside the basex home directory e.g. basex:read('222.readme'). I would like to be able to read files in basex queries as a non-admin user. But perhaps the admin restriction on this behaviour is by design? Cheers, Sandra

2 1

possible bug
by szabolcs kurdi 25 Jun '10

25 Jun '10

Hi! I'm not 100% sure if it is a bug in BaseX or it's just me, but maybe it's better to post it. The error below happens after importing lots of xml files (~100mb) and then calling Optimize - on Arch linux, inside Virtualbox. The same process finishes without problems on Windows XP. 0 [SwingWorker-pool-3-thread-1] ERROR com.rosamez.jdvdkat.DbManager - Could not optimize the db. Possible bug? Feedback is welcome: info(a)basex.org BaseX 6.1.7: java.lang.ArrayIndexOutOfBoundsException: 0 org.basex.util.Num.size(Num.java:84) org.basex.index.ValueBuilder.writeWithNum(ValueBuilder.java:176) org.basex.index.ValueBuilder.merge(ValueBuilder.java:125) org.basex.index.ValueBuilder.build(ValueBuilder.java:75) org.basex.index.ValueBuilder.build(ValueBuilder.java:1) org.basex.core.proc.ACreate.index(ACreate.java:116) org.basex.core.proc.ACreate.index(ACreate.java:91) org.basex.core.proc.Optimize.stats(Optimize.java:90) org.basex.core.proc.Optimize.run(Optimize.java:35) org.basex.core.Proc.run(Proc.java:140) org.basex.core.Proc.exec(Proc.java:110) org.basex.core.Proc.execute(Proc.java:67) com.rosamez.jdvdkat.DbManager.optimize(DbManager.java:240) com.rosamez.jdvdkat.AddAllFilesWorker.doInBackground(AddAllFilesWorker.java:34) com.rosamez.jdvdkat.AddAllFilesWorker.doInBackground(AddAllFilesWorker.java:14) javax.swing.SwingWorker$1.call(SwingWorker.java:277) java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) java.util.concurrent.FutureTask.run(FutureTask.java:138) javax.swing.SwingWorker.run(SwingWorker.java:316) java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) java.lang.Thread.run(Thread.java:619) Thanks! Szabolcs

2 4

Another Bug
by Dave Glick 23 Jun '10

23 Jun '10

I think I've found another bug (I promise I don't spend my whole day sitting around thinking of ways to break Basex). The test XML is at the bottom of this message. I'm not sure how to classify this bug, but consider the results of the following queries with the initial context set to <bbb>. Query: count(./preceding-sibling::*)+1 Result: 2 (as expected) Query: /test/a/ab/*[2] Result: <abb> (as expected) Query: /test/a/ab/*[count(./preceding-sibling::*)+1] Result: <aba><abb><abc> (was expecting just <abb> as before) This problem also appears to affect FLOWR expressions when using "for" but not "let"... Query: let $p := count(./preceding-sibling::*)+1 return /test/a/ab/*[$p] Result: <abb> (as expected) Query: for $p in 2 return /test/a/ab/*[$p] Result: <abb> (as expected) Query: for $p in count(./preceding-sibling::*)+1 return /test/a/ab/*[$p] Result: <aba><abb><abc> (was expecting just <abb> as before) Text XML: <test> <a> <aa/> <ab> <aba/> <abb/> <abc/> </ab> <ac/> </a> <ba/> <bb> <bba/> <bbb/> <bbc/> </bb> <bc/> </test>

2 4

BaseX - 5 stars rated on GearDownload.com
by gear＠geardownload.com 23 Jun '10

23 Jun '10

Dear DBIS Group, University of Konstanz, Your product, BaseX 6.1, has been tested 100% clean and rated 5 stars on GearDownload.com. Your product can be reached from the following URL: http://www.geardownload.com/business/basex.html If you want to link back to this page, you can use our 5 stars rating image (http://www.geardownload.com/images/5starsc.jpg) or choose more award images at http://www.geardownload.com/linktous.html to fit your site style. If you want to remove your product from our site or simply need something changed or updated, please feel free to contact us and we will work with you to fix any problem you may have found with the product's listing. You can upload your software file to GearDownload file server anytime by clicking on the following link: http://www.geardownload.com/submitfile.php?email=basex-talk@mailman.uni-kon… NEW! Free promotion is available now. Check at http://www.geardownload.com/promotion.php Thanks, Sincerely, The GearDownload Team gear(a)geardownload.com ====================================== NEW! Discuss software on our new forum. http://forum.geardownload.com ======================================

1 0

document-uri() and directory structure within collections
by C. M. Sperberg-McQueen 21 Jun '10

21 Jun '10

I've used BaseX to create a database of the XML Schema Test Suite, by specifying (in the GUI) the test suite's root directory and a filter of *.xml. (Well, to be completely explicit it's the root directory of a mirror in which each file is a symbolic link to the real test suite directories; this allows me to exclude ill-formed input and rename all XSD files as .xsd.xml.) But I find that when I retrieve an element $e and ask what document it was in, using document-uri($e), I do not get the expected result: I get the file name of the document, but I do not get the path to the document, only the path to the database root. For example: the BaseX database I'm working with was created by indexing directory /home/xmlschema/mirror-11. And for a query result element $a found in document /home/xmlschema/mirror-11/msData/additional/test73850.xml the expression document-uri($a/root()) returns /home/xmlschema/mirror-11/test73850.xsd.xml instead of the expected /home/xmlschema/mirror-11/msData/additional/test73850.xml (Side note: I do realize that the 'root()' in '$a/root()' is irrelevant; it's there to work around a bug in another XQuery processor, which shall remain nameless, which otherwise returns the empty sequence. Yes, it's true: I am seeing other XQuery engines as well as BaseX. I blush to admit it, because it makes me seem kind of promiscuous, but it's true.) Is this a bug? Did I do something wrong / set some parameter wrong when creating the database?) Is there a workaround? If it matters, I'm running BaseX 5.7 (cannot move to BaseX 6 at the moment because no Java 6 is available for my current hardware and software). -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net ****************************************************************

2 1

Fwd: Re: document-uri() and directory structure within collections
by Imsieke, Gerrit, le-tex 21 Jun '10

21 Jun '10

should go to the list, too... -------- Original Message -------- Subject: Re: [basex-talk] document-uri() and directory structure within collections Date: Mon, 21 Jun 2010 22:48:22 +0200 From: Imsieke, Gerrit, le-tex <gerrit.imsieke(a)le-tex.de> Organization: le-tex publishing services GmbH To: C. M. Sperberg-McQueen <cmsmcq(a)blackmesatech.com> I asked the same question recently. In reaction they implemented base-uri() in 6.1.4, which works as required. Reading the spec, I find it hard to recognize any semantic differences between base-uri() and document-uri(). Gerrit On 21.06.2010 22:37, C. M. Sperberg-McQueen wrote: > I've used BaseX to create a database of the XML Schema Test Suite, > by specifying (in the GUI) the test suite's root directory and > a filter of *.xml. (Well, to be completely explicit it's the > root directory of a mirror in which each file is a symbolic > link to the real test suite directories; this allows me to > exclude ill-formed input and rename all XSD files as .xsd.xml.) > > But I find that when I retrieve an element $e and ask what > document it was in, using document-uri($e), I do not get > the expected result: I get the file name of the document, > but I do not get the path to the document, only the path > to the database root. > > For example: the BaseX database I'm working with was created > by indexing directory /home/xmlschema/mirror-11. And for > a query result element $a found in document > /home/xmlschema/mirror-11/msData/additional/test73850.xml > the expression document-uri($a/root()) returns > > /home/xmlschema/mirror-11/test73850.xsd.xml > > instead of the expected > > /home/xmlschema/mirror-11/msData/additional/test73850.xml > > (Side note: I do realize that the 'root()' in '$a/root()' is > irrelevant; it's there to work around a bug in another XQuery > processor, which shall remain nameless, which otherwise > returns the empty sequence. Yes, it's true: I am seeing > other XQuery engines as well as BaseX. I blush to admit it, > because it makes me seem kind of promiscuous, but it's > true.) > > Is this a bug? Did I do something wrong / set some parameter > wrong when creating the database?) Is there a workaround? > > If it matters, I'm running BaseX 5.7 (cannot move to BaseX 6 > at the moment because no Java 6 is available for my current > hardware and software). > -- Gerrit Imsieke Geschäftsführer / Managing Director le-tex publishing services GmbH Weissenfelser Str. 84, 04229 Leipzig, Germany Phone +49 341 355356 110, Fax +49 341 355356 510 gerrit.imsieke(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

1 0

sayali Kulkarni wants to stay in touch on LinkedIn
by sayali Kulkarni 21 Jun '10

21 Jun '10

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - sayali Kulkarni sayali Kulkarni Looking for a job Pune Area, India Confirm that you know sayali Kulkarni https://www.linkedin.com/e/isd/1401339739/ZCnLLJ4a/ ------ (c) 2010, LinkedIn Corporation

1 0

create / aler problem
by szabolcs kurdi 19 Jun '10

19 Jun '10

Hi! I seem to have some problems with creating or renaming databases with dots in their names. From java using create (I'm using CreateColl) they are created fine, but from the gui the last set is truncated (something.dot1.dot2 -> something.dot1). Rename (AlterDB from 6.1.7) can't rename a db with dots in its name, but no BaseXException is raised. Is it a bug, or just using dots in the names (which are directory names of course) is not advised? Thanks! Szabolcs

2 1

XQuery FLOWR and Context
by Dave Glick 18 Jun '10

18 Jun '10

Hello again, You guys do such a great job of answering and responding to questions and concerns on this board, thanks again for that Christian. This next one might be a case of misunderstanding the standard on my part, but I'm seeing some odd things with XQuery when using a different initial context than the document root. Take the following XML: <test> <a> <aa/> <ab> <aba/> <abb/> <abc/> </ab> <ac/> </a> <ba/> <bb> <bba/> <bbb/> <bbc/> </bb> <bc/> </test> Here is the result of several different XQuery commands with different initial contexts (I've loaded the document into the BaseX GUI and am setting initial context by double-clicking the element in the grid view)... Query: . Context: document, Result: The entire document (as expected) Context: , Result: The element and all its content (as expected) Query: let $v := . return $v Context: document, Result: The entire document (as expected) Context , Result: The entire document (was expecting the element and all its content!) Query: .//ab Context: document, Result: Result: The <ab> element and its content (as expected) Context , Result: Nothing (as expected) Query: let $v := //ab return $v Context: document, Result: The <ab> element and its content (as expected) Context: , Result: The <ab> element and its content (as expected) Query: let $v := .//ab return $v Context: document, Result: The <ab> element and its content (as expected) Context: , Result: The <ab> element and its content (was expecting nothing!) As you can see, it seems to behave counter to expectations when the initial context is not the document and I use the initial context in the FLOWR expression. I attempted to test in other tools, but it appears that setting the initial context for an XQuery expression is actually a difficult feature to find. It's not a totally academic question, though - the system we're building uses initial contexts pretty extensively. I know that context is not maintained in XQuery, but can the initial context not be used in variable assignment or other components of a FLOWR expression? Thanks, Dave

2 2

tablemem
by NewIntellectual 18 Jun '10

18 Jun '10

I've tried to figure out how to use the described 'tablemem' command ("Loading database table into main memory and speedup evaluation times"), unsuccessfully so far. Can this be invoked both in the BaseX GUI and in a client call to the server? Surely it would only make sense to make the call once after server startup.

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk June 2010