predicate evaluation issue
Wednesday, 10 November 2010 · 4 messages
MG
Martin Gieseking10 Nov 2010 17:17 #
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
CG
Christian Grün10 Nov 2010 17:29 #
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
Quoted text · Martin Gieseking · 21 lines
On Wed, Nov 10, 2010 at 5:17 PM, Martin Gieseking <martin.gieseking at 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 at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
MG
Martin Gieseking10 Nov 2010 17:42 #
Thank you for the prompt fix, Christian. Next time I try to find something more challenging. :)
Regards,
Martin
Quoted text · Christian Grün · 33 lines
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 at 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 at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >
CG
Christian Grün10 Nov 2010 17:42 #
Looking forward... ;)
Christian
Quoted text · Martin Gieseking · 52 lines
On Wed, Nov 10, 2010 at 5:42 PM, Martin Gieseking <martin.gieseking at uos.de> wrote: > 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 at 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 at mailman.uni-konstanz.de >>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>> >> > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
Written for BaseX 6. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery