Hello Dave,
thanks again for your helpful report. The obvious bug has been fixed; feel free to check out the latest sources.
All the best, Christian
On Fri, Apr 9, 2010 at 12:08 AM, Dave Glick dglick@dracorp.com wrote:
Hello,
I think I've found a possible bug. I've attached a source XML file. The following query returns 36 results in the most recent BaseX version (updated today and built from source):
/Region/Sections/Section[./V[@id='Section_ID']='"Maritime Environment Regions"']//RegionList/Region
However, I think it should be returning 10 results (and indeed it does in previous versions of BaseX as well as Saxon). The interesting part is that it does return a single result (as expected) for the first part of the query:
/Region/Sections/Section[./V[@id='Section_ID']='"Maritime Environment Regions"']
...so it appears as though the last part of the query (//RegionList/Region) is descending from the root and not from the single node returned in the first part as I would expect. Is this a bug in BaseX or a misunderstanding on my part of some subtlety of the standard?
Thanks,
Dave
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk