the 1.0b2 release already shows the same wrong behaviour. But the
problem seems easy to fix. I attach a patch against the current CVS.
Hope it works as expected...
> Looks like there is indeed a bug here (maybe a regression of recent date,
> because I'm fairly sure this used to work correctly), which seems to affect
> all the functions as well as the operators that use the fulltext index
> find match-any(//usg,'d.*')
> on one of my collections should return nothing, but in fact it returns 8125
> false positives, because it is matching an attribute value. eg here
> <usg type="dom">bot.</usg>
> This is with cvs of 2005-02-18, the most recent build I have to hand at the
> moment. Can't try with anything more recent right now because the
> sourceforge cvs won't talk to me (it seems to refuse service if the first
> nameserver listed for a would-be client's domain is down, as is the case
> with my domains at the moment)
Get latest updates about Open Source Projects, Conferences and News.