Thank you for the prompt fix, Christian. Next time I try to find something more challenging. :)
Regards, Martin
Am 10.11.2010 17:29, schrieb Christian Grün:
Martin,
thanks again for your diligent debugging; once more, I'm surprised this special case wasn't covered before. I've committed a fix on this one as well.
Christian
On Wed, Nov 10, 2010 at 5:17 PM, Martin Gieseking martin.gieseking@uos.de wrote:
Hello again, :)
I think, I've found another bug. This time it's somehow related to implicit type casting. When running the query /a/b[@*=2] on the following XML document, both b nodes are selected, although the first one has no matching attribute. /a/b[@*='2'] returns the correct node.
<a> <b a="1" b="3"/> <b a="2" b="2"/> </a>
Best regards, Martin _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk