This info is not provided by the API (or I missed it). I required this for a ranking that considers both the distance of N matches to each other, and the offset of those matches to the beginning of a text. I worked around this by giving a boost for the byte distance of the words (taking into account the length in bytes of a phrase, phrases with less byte distance to each other as provided in the order of their appearance of the match statement get a slightly higher boost).
This worked Ok as approximation. Depending how your ranking needs to be calculated, you¹d however maybe better use a custom extra fts info table and fill this info yourself. Am 17.06.14 02:58 schrieb "Josh Wilson" unter <neozenith....@gmail.com>: >Ok so I have found the following guides: > >http://www.sqlite.org/privatebranch.html > >http://www.sqlite.org/src/doc/trunk/README.md > >So as far as creating a private branch 'the proper way' this should be >sufficient but as far as getting the token positions for FTS MATCH results >any advice on the topic is appreciated. > > > >-- >View this message in context: >http://sqlite.1065341.n5.nabble.com/Proximity-ranking-with-FTS-tp76149p761 >50.html >Sent from the SQLite mailing list archive at Nabble.com. >_______________________________________________ >sqlite-users mailing list >sqlite-users@sqlite.org >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
