Re: [Exist-open] differing behavior with qname range index

[Adam R. <ad...@ex...>]

Always the first question - what version of eXist are you using?


Some thoughts... (although I have to admin I am not an expert on the
indexing stuff)

> then the following xpath works:
> //*[@pageid = "31804"]
> When I add the qname integer index, it fails.

You are indexing an integer, but looking for a string (note the
quotes). In this instance I would expect it not to use the index, but
to fall back to an un-indexed approach, still finding the result but
without using the index.

But in this instance -

//*[@pageid = 31804]

I would expect it to find the result via. the integer index that you created.

> presence of the index would only affect performance, not query results.

Indeed, as would I.

> So I am forced to do this:
> //*[xs:integer(@pageid) = 31804]

I would imagine that you do not need the explicit xs:integer
construction part there, but I may be wrong...




-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb