Talk:Places:Full Text Indexing

It sounds like a lot of what you're discussing here matches what we did for fts1 in SQLite. fts2 was a great improvement in terms of performance, and has no breaking changes expected. I'm considering folding in ability to index external content for fts3, but customers actually talking to me get some priority :-).

[shess at google dot com]

Have gone through fts2 again. Looks promising. FTS2 does not support indexing extenal content. Although, this is not ideal, we are still going for this looking at other benefits. Also, FTS3, Scott hints, will have an API similar to FTS2. Will update the wiki with update design very soon. However the basic tasks are as follows:

1. Build Mozilla with FTS2 support
2. Design Database Table
3. Code for table generation in nsNavHistory.cpp
4. nsNavFullTextIndexHelper will remain the same
5. UI
6. Tokenizer System
7. Support for other Languages
8. Performance
9. Test

[vertex3d2004 at gmail dot com]