BaseX-Talk

basex-talk@mailman.uni-konstanz.de

4 participants
5268 discussions

Fwd: Having trouble inserting elements using XQJ two times with the same prepared expression
by Stefano Santoro 02 Jun '10

02 Jun '10

Hi Lukas, just to be thorough I tried all the steps I have described in my earlier e-mail on a different workstations running a different OS (linux), and the attempt yielded the same Exception. Ciao Stefano On Fri, May 28, 2010 at 1:14 PM, Stefano Santoro <stefano(a)santoro.org> wrote: > Hi Lukas, > > Interesting. I have gotten all your maven repository jar files and > included them in the class path as follows: > > $ echo $GVYCP > C:\opt\jlib\basex-api\xmldb-api-1.0.jar;C:\opt\jlib\basex-api\xqj-api-1.0.jar;C:\opt\jlib\basex-api\basex-api-6.1.3.jar;C:\opt\jlib\basex-api\basex-6.1.3.jar > > the same but more clearly listed > > $ dvcp GVYCP > 0) C:\opt\jlib\basex-api\xmldb-api-1.0.jar > 1) C:\opt\jlib\basex-api\xqj-api-1.0.jar > 2) C:\opt\jlib\basex-api\basex-api-6.1.3.jar > 3) C:\opt\jlib\basex-api\basex-6.1.3.jar > > I have run the same java class I have enclosed in the earlier version > as follows: > > $ java -version > java version "1.6.0_17" > Java(TM) SE Runtime Environment (build 1.6.0_17-b04) > Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing) > > $ java -cp ".;${GVYCP}" NPEReproducer > java.lang.ArrayIndexOutOfBoundsException: 5 > at org.basex.query.up.Primitives.add(Primitives.java:52) > at org.basex.query.up.DBPrimitives.add(DBPrimitives.java:40) > at org.basex.query.up.Updates.add(Updates.java:90) > at org.basex.query.up.Insert.atomic(Insert.java:102) > at org.basex.query.up.Insert.atomic(Insert.java:30) > at org.basex.query.expr.Expr.iter(Expr.java:58) > at org.basex.query.QueryContext.iter(QueryContext.java:322) > at org.basex.query.QueryContext.iter(QueryContext.java:290) > at org.basex.api.xqj.BXQDynamicContext.execute(BXQDynamicContext.java:246) > at org.basex.api.xqj.BXQPreparedExpression.executeQuery(BXQPreparedExpression.java:54) > at NPEReproducer.reproduceNPE(NPEReproducer.java:51) > at NPEReproducer.main(NPEReproducer.java:60) > > I have also checked out your basex trunk and was able to build > basex-6.1.3.jar, and even with that jar the same exception was thrown. > > I was not able to build the api maven project as it could not resolve > the jax-rx dependency.(see attached log) > > I was able though to build an api jar from your trunk that contained > only the xml:db and XQJ drivers from trunk, and with that too the same > exception was thrown. > > So I have tried with the jars that I have downloaded from: > > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/xmldb/xmldb-api/1.0/xml… > http://www.inf.uni-konstanz.de/dbis/basex/maven/javax/xml/xquery/xqj-api/1.… > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex-api/6.1.3/b… > http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.1.3/basex… > > I have also built basex-6.1.3.jar and basex-6.1.3.jar (w/o jaxrx) from > your trunk, and yet I was not able to run it as you were able to do. > > Is there anything I am missing? > > Ciao > Stefano > > > > On Fri, May 28, 2010 at 9:15 AM, Lukas Kircher > <lukaskircher1(a)googlemail.com> wrote: >> Hey Stefano, >> >> thanks for your report. >> >>> I am enclosing a java class file that reproduces this problem against >>> 6.1.3 basex jar files >> >> >> Unfortunately I wasn't able to reproduce the exception by running your >> code - neither with version 6.1.3 nor with our current repository version. >> It runs fine on my machine. Do you have a clue where I could've missed >> something? >> >> Or - if you have another case at hand where you encounter the same problem, >> just let us know and we'll see what we can do. >> >> Kind regards, >> Lukas >> >

2 2

Fwd: Re: dropping DataBase
by Leonard Wörteler 30 May '10

30 May '10

Hi Bea, i didn't realize that you're not on the basex-talk list. Sorry for that. Leo -------- Original-Nachricht -------- Betreff: Re: [basex-talk] dropping DataBase Datum: Sun, 30 May 2010 18:34:42 +0200 Von: Leonard Wörteler <leo(a)woerteler.de> An: basex-talk(a)mailman.uni-konstanz.de Hi again, Just in case you're interested: A simple way to create a main-memory based DB in BaseX, given the path to an XML document, would be final Data db = CreateDB.xml(IO.get(path), CTX.prop); CTX.openDB(db); // open DB in current Context By the way, this also works if you feed IO.get(..) an XML string instead of a path. Cheers again, Leo Am 30.05.2010 17:10, schrieb Leonard Wörteler: > Hello Beatriz, > > Am 30.05.2010 16:32, schrieb Beatriz Sancho: >> static public Vector queryExtraeDatosCabecera(final String query) throws >> BaseXException, QueryException, IOException { >> WorkSpace sp1 = new WorkSpace(); >> String workspace = sp1.getWorkspace(); >> new CreateDB(workspace + "\\cabecera.xml", "DBCabecera").execute(CONTEXT); >> [...] >> new DropDB("DBCabecera").execute(CONTEXT); >> return datos; >> } > > wouldn't it be much easier to use an in-memory DB in this case? No need > to explicitly drop it and you probably would even get better performance > because of reduced I/O. > > Just my 0.02$...

2 1

dropping DataBase
by bea.sancho＠gmail.com 30 May '10

30 May '10

Do you have any idea about this? org.basex.core.BaseXException: Database could not be dropped. at org.basex.core.Proc.execute(Proc.java:75) when it does: new DropDB("DBCabecera").execute(CONTEXT); My program is doing a lot of actions to get some information and sometimes this error appears, do you know why? How can i solve it? Another question, what would happen if I create a lot of news DB with the same name and i don't drop them? Thank you very much!

5 4

nasty bug with xquery empty sequence ()
by Sandra Maria Silcot 30 May '10

30 May '10

To basex developers, The following xquery returns 464 <persName> elements with saxonHE but fails to produce any <persName> elements when the query is run in basex (6.1.3). for $RT in ("c31a") let $theseRecs := //c31a[sourceVol="CON 31/2"] let $ctr := count($theseRecs) let $pList := <listPersName n="{$ctr}">{ for $p at $i in $theseRecs let $conref := if ( $RT = "c37v" ) then <hi/> else () return <persName id="{$p/@xml:id}">{$i}</persName> }</listPersName> return ( $pList,<hello/> ) If the xquery null sequence () in line 6 is changed to an empty string: else "" I get the expected 464 results. With () in the else I get only this: <listPersName n="464"/> <hello/> I had a devil of a time detecting this. I also have encountered bad behaviour when running queries against attributes which exist but have no value, like this: <el attr=""> In Saxon I can search for //el[@attr=""] and get results but basex does not find these cases. Hoping these bugs can be quickly squashed. regards, Sandra

2 1

Re: [basex-talk] Having trouble inserting elements using XQJ two times with the same prepared expression
by Stefano Santoro 29 May '10

29 May '10

Hi Lukas, Interesting. I have gotten all your maven repository jar files and included them in the class path as follows: $ echo $GVYCP C:\opt\jlib\basex-api\xmldb-api-1.0.jar;C:\opt\jlib\basex-api\xqj-api-1.0.jar;C:\opt\jlib\basex-api\basex-api-6.1.3.jar;C:\opt\jlib\basex-api\basex-6.1.3.jar the same but more clearly listed $ dvcp GVYCP 0) C:\opt\jlib\basex-api\xmldb-api-1.0.jar 1) C:\opt\jlib\basex-api\xqj-api-1.0.jar 2) C:\opt\jlib\basex-api\basex-api-6.1.3.jar 3) C:\opt\jlib\basex-api\basex-6.1.3.jar I have run the same java class I have enclosed in the earlier version as follows: $ java -version java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing) $ java -cp ".;${GVYCP}" NPEReproducer java.lang.ArrayIndexOutOfBoundsException: 5 at org.basex.query.up.Primitives.add(Primitives.java:52) at org.basex.query.up.DBPrimitives.add(DBPrimitives.java:40) at org.basex.query.up.Updates.add(Updates.java:90) at org.basex.query.up.Insert.atomic(Insert.java:102) at org.basex.query.up.Insert.atomic(Insert.java:30) at org.basex.query.expr.Expr.iter(Expr.java:58) at org.basex.query.QueryContext.iter(QueryContext.java:322) at org.basex.query.QueryContext.iter(QueryContext.java:290) at org.basex.api.xqj.BXQDynamicContext.execute(BXQDynamicContext.java:246) at org.basex.api.xqj.BXQPreparedExpression.executeQuery(BXQPreparedExpression.java:54) at NPEReproducer.reproduceNPE(NPEReproducer.java:51) at NPEReproducer.main(NPEReproducer.java:60) I have also checked out your basex trunk and was able to build basex-6.1.3.jar, and even with that jar the same exception was thrown. I was not able to build the api maven project as it could not resolve the jax-rx dependency.(see attached log) I was able though to build an api jar from your trunk that contained only the xml:db and XQJ drivers from trunk, and with that too the same exception was thrown. So I have tried with the jars that I have downloaded from: http://www.inf.uni-konstanz.de/dbis/basex/maven/org/xmldb/xmldb-api/1.0/xml… http://www.inf.uni-konstanz.de/dbis/basex/maven/javax/xml/xquery/xqj-api/1.… http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex-api/6.1.3/b… http://www.inf.uni-konstanz.de/dbis/basex/maven/org/basex/basex/6.1.3/basex… I have also built basex-6.1.3.jar and basex-6.1.3.jar (w/o jaxrx) from your trunk, and yet I was not able to run it as you were able to do. Is there anything I am missing? Ciao Stefano On Fri, May 28, 2010 at 9:15 AM, Lukas Kircher <lukaskircher1(a)googlemail.com> wrote: > Hey Stefano, > > thanks for your report. > >> I am enclosing a java class file that reproduces this problem against >> 6.1.3 basex jar files > > > Unfortunately I wasn't able to reproduce the exception by running your > code - neither with version 6.1.3 nor with our current repository version. > It runs fine on my machine. Do you have a clue where I could've missed > something? > > Or - if you have another case at hand where you encounter the same problem, > just let us know and we'll see what we can do. > > Kind regards, > Lukas >

3 2

rename database
by szabolcs kurdi 29 May '10

29 May '10

Hi! I'm trying to embed BaseX into a smaller java project - pretty much everything works perfectly, but I can't seem to find a way to rename an existing database: am I missing something? I use CreateDB, DropDB and InfoDB - is there something like RenameDB? Or shall I try to rename the directory at the user's home dir in BaseXData? Thank you! Szabolcs Kurdi PS: probably it is widely known, but in the gui the query editor is badly broken with international keyboards (like using the AltGr key).

2 1

Having trouble inserting elements using XQJ two times with the same prepared expression
by Stefano Santoro 27 May '10

27 May '10

Hi Christian, when I try to reuse the same prepared expression the second time with a different bound document I get the following array out of bound exception: java.lang.ArrayIndexOutOfBoundsException: 5 at org.basex.query.up.Primitives.add(Primitives.java:52) at org.basex.query.up.DBPrimitives.add(DBPrimitives.java:40) at org.basex.query.up.Updates.add(Updates.java:91) at org.basex.query.up.Insert.atomic(Insert.java:102) at org.basex.query.up.Insert.atomic(Insert.java:1) at org.basex.query.expr.Expr.iter(Expr.java:53) at org.basex.query.QueryContext.iter(QueryContext.java:322) at org.basex.query.QueryContext.iter(QueryContext.java:290) at org.basex.api.xqj.BXQDynamicContext.execute(BXQDynamicContext.java:246) at org.basex.api.xqj.BXQPreparedExpression.executeQuery(BXQPreparedExpression.java:54) at NPEReproducer.reproduceNPE(NPEReproducer.java:51) at NPEReproducer.main(NPEReproducer.java:60) I am enclosing a java class file that reproduces this problem against 6.1.3 basex jar files Ciao Stefano

1 0

Having trouble inserting elements using XQJ
by stefano＠santoro.org 26 May '10

26 May '10

Hi, I am attempting to execute an XQJ prepared expression that uses an external bind variable that accepts an xml element, and inserts it into the database document: declare variable $inserto as element(*,xs:untyped) external; let $root := basex:db('Annotations')/Annotations return (insert node $inserto into $root) I prepare the above statement and I bind DOM element as follows (groovy syntax): eltype = conn.createElementType(null, XQItemType.XQBASETYPE_ANYTYPE); ixpr.bindNode(new QName("inserto"), irel, eltype); irel is dom element that serializes as follows: <inserto id="6"> <testo>six</testo> </inserto> unfortunately I get an NPE when I try to execute the Query: groovy:000> rs = ixpr.executeQuery() ERROR java.lang.NullPointerException: null at org.basex.query.item.FElem.copy (FElem.java:214) at org.basex.query.item.FElem.copy (FElem.java:1) at org.basex.query.item.FElem.copy (FElem.java:210) at org.basex.query.item.FElem.copy (FElem.java:1) at org.basex.query.expr.Constr.add (Constr.java:107) at org.basex.query.expr.Constr.<init> (Constr.java:53) at org.basex.query.up.Insert.atomic (Insert.java:60) at org.basex.query.up.Insert.atomic (Insert.java:1) at org.basex.query.expr.Expr.iter (Expr.java:53) at org.basex.query.QueryContext.iter (QueryContext.java:322) at org.basex.query.QueryContext.iter (QueryContext.java:290) at org.basex.api.xqj.BXQDynamicContext.execute (BXQDynamicContext.java:247) at org.basex.api.xqj.BXQPreparedExpression.executeQuery (BXQPreparedExpression.java:54) at groovysh_evaluate.run (groovysh_evaluate:10) ... I am using BaseX 6.1 Am I doing anything wrong? Stefano

3 4

gui version possible bug with handling xml attributes?
by Sandra Maria Silcot 26 May '10

26 May '10

Hello all, I am experiencing this odd behaviour in the gui version of basex v6.1 on windows xp. When using the Explorer panel and I choose an attribute (prefixed with "@"), the query info panel reports: Error: [XPST0003] Unexpected end of query: '@seriesId[text(...'. It presents the attribute values correctly in the drop down display, but if I select a value or try to filter, nothing happens and the error message is repeated. It looks like it thinks its processing an element. Shouldn't attribute queries be written as "data(@attrName)"? I am not sure when this crept in. Is anyone else experiencing this behavior? I am getting this on any xml document having attributes in the gui version. Thanks for any insight. Cheers all, Sandra

3 4

Congruence of documents and database nodes
by Hans-Peter Oeri 25 May '10

25 May '10

Hi! Within the documentation[1], you note that XQuery Updates are not reflected in the documents. There is an example of how to write queries that use fn:put to do such an update manually. Under the assumption that XQueries and updates are far more frequent than document puts/pulls, wouldn't an 'inversed' technique be favorable? One that updates "dirty" documents upon fetching them rather than updating with each and every query? (Plus, as far as I see, not needing manual fn:puts is more interoperable) Unfortunately, such 'inversion' would not only need an update to the API classes, but also the "core" (as "dirty" documents would need to be flagged). Would that be a reason the current implementation got as it is? Or don't I see some other issue? HPO [1] http://www.inf.uni-konstanz.de/dbis/basex/xquery#update

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk