Re: [basex-talk] ft:mark and differing result sets on 10.2

2022-10-05 Thread Chris Yocum
Hi Christian, Thank you very much for your comments on this. I ended up doing this: ft:mark(ft:search("edil-new", "fas", map {"wildcards":"true"})/ancestor::entry) which gives me everything that I was expecting and is performant as expected. Basically, I took this: for $x in

Re: [basex-talk] ft:mark and differing result sets on 10.2

2022-10-05 Thread Christian GrĂ¼n
Hi Chris, > for $x in db:get($db)/sample/entry > return ft:mark($x[descendant::text() contains text {'fas'} using wildcards]) > > which ran in 2528.78ms and return 170 results. This seemed rather > slow so I started to work on it. I also ran this: > > for $x in db:get($db)/sample/entry > return

Re: [basex-talk] ft:mark and differing result sets on 10.2

2022-10-02 Thread Christopher Yocum
Hi Everyone, I just had a follow up on the issue that I had. I think I figured out at least one thing. I had diacritics set as true so it was only returning those results without diacritics so I was able to get the two queries to return the same results and go faster. However I ran into a new

[basex-talk] ft:mark and differing result sets on 10.2

2022-10-02 Thread Chris Yocum
Hi, I had a chance to come back to basex after a while when I needed to do some querying on my data set. I updated to 10.2 and loaded the files. This was all fine. I then ran this query: for $x in db:get($db)/sample/entry return ft:mark($x[descendant::text() contains text {'fas'} using