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

Re: [basex-talk] ft:mark

2015-07-05 Thread Christian Grün
Hi Lars, I guess it was due to the internal XQFT representation of match positions that adjacent matches are marked one by one, and it's probably difficult to change this without too much additional effort. However, you can use XQuery for transforming your result; see e.g. the attached XQuery

Re: [basex-talk] ft:mark

2015-07-05 Thread Lars Johnsen
Thanks for XQuery code! I will try to integrate it with our own efforts, and let you know how it goes. Lars 2015-07-05 15:19 GMT+02:00 Christian Grün christian.gr...@gmail.com: Hi Lars, I guess it was due to the internal XQFT representation of match positions that adjacent matches are

[basex-talk] ft:mark

2015-07-02 Thread Lars Johnsen
The full text function ft:mark() puts a mark around each of the words that occur in a match, starting from the first matching word to the last, including stop words, except for punctuation characters. Is it possible to check for the kind of characters (or strings) that ft:mark() will skip when