On Sun, Oct 17, 2010 at 11:13 PM, Dami Laurent (PJ) <laurent.d...@justice.ge.ch> wrote: >>Is it possible to use FTS3 for search without storing the actual file >>contents/search terms/keywords in a row. In other words, create a FTS3 >>tables with rows that only contains an ID and populate the B-Tree with >>keywords for search. > > Each FTS3 table t is stored internally within three regular tables : > t_content, t_segments and t_segdir. The last two tables contain the > fulltext index. The first table t_content stores the complete documents > being indexed, and is only used when you call the offsets() or > snippets() functions. So if you don't need those functions, you can > cheat : a) call FTS3 to index your document as usual; b) do an update on > the t_content table to remove the document text.
If you do this, it is probably safest to replace the columns in the content table with empty strings, rather than deleting them entirely. It won't remove all the untested edge cases, of course! Doing this will prevent various things from working, and nobody is likely to have ready answers for how it breaks. For instance, updating or deleting from the fts3 table will have unexpected results (it needs the original document to update the index), phrase or near searches won't work (but might claim to work, with empty results), and the snippet/offset code won't work (again, probably will just show empty results). -scott _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
