Thanks Marbex, Puneed and specially to Scott for the snippet() tip.
'ined' is Porter stemmed to 'in'! :-)
So that is why it finds so many rows.
Now, to find 17081 rows from a table with 25672, fts3 took 4.47 seconds!
The query is:
select title from fts_news where description match 'in'
If I execute a similar query with 'like':
select title from fts_news where description like '% in %'
It takes only 1.36 seconds. 3.2 x faster for a sequential search vs an fts3
one!
The point is that it seems that fts3 gets slower as the number of rows it
has to return grows.
Jochi Martinez
www.bfreenews.com
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
