Recent changes to bugs

error executing query

Anonymous — Tue, 15 May 2012 12:18:31 -0000

Hi, i was executing this query:

declare variable $doc external;

declare function local:yyyymmdd-to-date
( $dateString as xs:string? ) as xs:dateTime? {

if (empty($dateString))
then ()
else if (not(matches($dateString,
'^\D*(\d{4})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*$')))
then error(xs:QName('local:Invalid_Date_Format'))
else fn:dateTime(xs:date(replace($dateString,
'^\D*(\d{4})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*$',
'$1-$2-$3')),xs:time(replace($dateString,
'^\D*(\d{4})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*(\d{2})\D*$',
'$4:$5:$6')))
} ;

declare function local:getLastDate () as xs:dateTime? {
for $x in $doc//sample[@counter=0]
return local:yyyymmdd-to-date($x/date)
};

declare function local:getDateDiffInMinutes ($date1 as xs:dateTime?, $date2 as xs:dateTime?) as xs:int? {
if ($date1 >= $date2)
then fn:hours-from-duration($date1 - $date2) * 60 +
fn:minutes-from-duration($date1 - $date2)

else fn:hours-from-duration($date2 - $date1) * 60 +
fn:minutes-from-duration($date2 - $date1)

};

for $d in distinct-values($doc//queue/@queuename)
let $items := $doc//queue[@queuename=$d]
order by $d
return <queue queuename="{$d}">{
for $i in $items
where local:getDateDiffInMinutes(local:getLastDate (), local:yyyymmdd-to-date($i/..//sample/date)) < 2 (: error is here :)
order by $i//numcallsinqueue
return $i//numcallsinqueue
}</queue>

And this error retourned:

javax.xml.xquery.XQQueryException: ch.ethz.mxquery.exceptions.DynamicException: parent not working here - please report
at ch.ethz.mxquery.xqj.MXQueryXQForwardSequence.next(MXQueryXQForwardSequence.java:255)
at ch.ethz.mxquery.xqj.MXQueryXQDataFactory.createSequence(MXQueryXQDataFactory.java:428)
at XQJExample.main(XQJExample.java:115)

in attachment the xml that has been loaded into $doc.

NPE in DocOrderCompare - suggested fix

W.Hummer — Sun, 29 Apr 2012 23:00:28 -0000

Executing the following query with MXQuery SVN snapshot dated 2012-04-04 yields a NPE:

for tumbling window $w in $input
start when true()
end when true()
return $w/(for $i in //random return $i)

"$input" is a sequence of "<random/>" elements. I'm aware that the query could be easily re-formulated, but we require this syntax for certain application-specific reasons.

The following modification to ch.ethz.mxquery.iterators.DocOrderCompare seems to fix the issue:

public class DocOrderCompare implements Comparator {

public int compare(Object o1, Object o2) throws MXQueryException {
Identifier i0 = ((DocOrderObject)o1).getIdentifier();
Identifier i1 = ((DocOrderObject)o2).getIdentifier();

/* start fix */
if(i0 == null || i1 == null)
return 0;
/* end fix */

int c = i0.getStore().compare(i1.getStore());
if(c == 0){
int i = i1.compare(i0);
if(i==0)
return 0;
else if(i==1)
return 1;
else
return -1;
}
else
return c;
}

}

Very good article post.Really thank you! Really Cool.

Anonymous — Mon, 26 Mar 2012 11:09:26 -0000

Very good article post.Really thank you! Really Cool.

aPcmaR Appreciate you sharing, great article post. Fantastic

Anonymous — Fri, 23 Mar 2012 05:16:08 -0000

aPcmaR Appreciate you sharing, great article post. Fantastic.

NPE after catch22 problem

Anonymous — Thu, 24 Mar 2011 17:04:42 -0000

I am trying to run the following code:

01: XQDataSource xqDS = new MXQueryXQDataSource();
02: XQConnection xqConn = xqDS.getConnection();
03: XQPreparedExpression xqPExpr = xqConn.prepareExpression(new FileInputStream(new File(xqInputPath)));
04: xqPExpr.bindDocument(new QName("xPRSXMLInput"),new FileInputStream(xmlInputPath), null, null);

This fails in 04 with a NPE, see stacktrace:

Exception in thread "main" java.lang.NullPointerException
at ch.ethz.mxquery.iterators.VariableIterator.firstInit(VariableIterator.java:96)
at ch.ethz.mxquery.iterators.VariableIterator.setResettable(VariableIterator.java:170)
at ch.ethz.mxquery.model.Iterator.setResettable(Iterator.java:217)
at ch.ethz.mxquery.model.Iterator.setResettable(Iterator.java:217)
at ch.ethz.mxquery.model.Iterator.setResettable(Iterator.java:217)
at ch.ethz.mxquery.iterators.FFLWORIterator.setResettable(FFLWORIterator.java:335)
at ch.ethz.mxquery.iterators.FFLWORIterator.<init>(FFLWORIterator.java:61)
at ch.ethz.mxquery.iterators.FFLWORIterator.copy(FFLWORIterator.java:451)
at ch.ethz.mxquery.iterators.FFLWORIterator.copy(FFLWORIterator.java:436)
at ch.ethz.mxquery.model.Iterator.copy(Iterator.java:593)
at ch.ethz.mxquery.bindings.WindowBuffer.copy(WindowBuffer.java:438)
at ch.ethz.mxquery.bindings.WindowSequenceIterator.copy(WindowSequenceIterator.java:369)
at ch.ethz.mxquery.model.Iterator.copy(Iterator.java:603)
at ch.ethz.mxquery.model.VariableHolder.copy(VariableHolder.java:190)
at ch.ethz.mxquery.contextConfig.Context.copy(Context.java:1529)
at ch.ethz.mxquery.query.impl.PreparedStatementImpl.copy(PreparedStatementImpl.java:155)
at ch.ethz.mxquery.xqj.MXQueryXQPreparedExpression.<init>(MXQueryXQPreparedExpression.java:52)
at ch.ethz.mxquery.xqj.MXQueryXQConnection.prepareExpression(MXQueryXQConnection.java:175)
at ch.ethz.mxquery.xqj.MXQueryXQConnection.prepareExpression(MXQueryXQConnection.java:151)
at ch.ethz.mxquery.xqj.MXQueryXQConnection.prepareExpression(MXQueryXQConnection.java:125)
at ch.ethz.mxquery.xqj.MXQueryXQConnection.prepareExpression(MXQueryXQConnection.java:118)
at myValidator.main(myValidator.java:57)

xqInputPath points to an xquery file that holds this snippet:

declare variable $xPRSXMLInput as document-node(element(*, xs:untyped)) external;
declare variable $rootelement_first := $xPRSXMLInput/prin:OfferExtraction;

What is happening here is that I am basing a variable (rootelement_first ) on an external variable (perfectly legit), however mxquery tries to interpret that before I have a chance to set it. Tested with mxquery-0.6.0 on Java 1.6.0_21. Reproduceable.

Module importation doesn't work

Anonymous — Sun, 18 Apr 2010 12:15:39 -0000

Hello,
I think that module importation is broken. When importing a library module that defines functions, the query parser apparently doesn't import the target namespace, and consequently fails to register the imported functions into the main modules's context.

Example:

(: module libmod.xq :)
module namespace libmod = "libmod" ;

declare function libmod:hello() as element() {
<hello>world</hello>
} ;

(: module mainmod.xq :)
import module namespace libmod = "libmod" at "libmod.xquery" ;

libmod:hello()

Trying to run mainmod.xq fails, complaining that the libmod prefix is in an unallocated namespace.

Any help would be greatly appreciated :-)

xquery serialization parameters are incorrect

Matthew L Daniel — Thu, 11 Mar 2010 23:58:47 -0000

According to XQuery spec, which references the "XSLT 2.0 and XQuery 1.0 serialization" spec (http://www.w3.org/TR/xslt-xquery-serialization/), the serialization option "indent" accepts only the tokens "yes" or "no" (http://www.w3.org/TR/xslt-xquery-serialization-11/#serparam). The same holds for XQ 1.1 (and XSLT/XQ serialization 1.1).

The 0.6.0 release only accepts "true" or "anything other than 't' 'r' 'u' 'e'".

And, further, the "undeclare-prefixes" option is mis-implemented as "undeclared-prefixes".

XDMSerializer escapes already escaped &

Stivo — Wed, 30 Dec 2009 12:38:06 -0000

I found the problem in changeEntityRef.
I propose to exchange:
val = Utils.replaceAll(val, "&", "&");
with:
val = val.replaceAll( "&(?!(#\\d+;|amp;))", "&");
This worked for my use cases at least fine.

fn:resolve-uri implementation wrong in some cases

Stivo — Wed, 23 Dec 2009 14:17:49 -0000

Running a query like:
String query = "resolve-uri('/','http://example.com/bla/asdf/')";
gives this output
http://example.com/bla/asdf//
However, this should be:
http://example.com/

I replaced some code using the java library to do this stuff, which handles this case well and most likely all others too...
Surpisingly URIUtils.resolveURI also outputs a wrong result.

text() does not work correctly on external input

Stivo — Tue, 22 Dec 2009 23:28:59 -0000

I have the attached test case.
The expected output is:
1 & 2 & 3
5
<?xml version='1.0' encoding='UTF-8' ?>
42
Like I get when I use query2 or query3 instead of query1.
The actual output is:
1
&
<?xml version='1.0' encoding='UTF-8' ?>
42
It seems to split incorrectly at the ampersand in this case...