Re: [Tracker] Anaylsis of Sqlite FTS 3

["Ivan Frade" <ivan frade gmail com>]

Hi Jamie

 This FTS3 sounds great, and could help to remove a lot of "home brew" code.

> All the above disadvantages can be sorted by forking FTS 3 and
> including:

 well, "forking" doesn't sound so good. Specially talking about sqlite
that moves very fast. I dont know the technical details but sqlite
should have places to connect the parsing functions and scoring
algorithms. Something similar to the "collation" functions for the
traditional tables. If it didnt have those things, we can think on add
them.

> I will likely try and integrate this when we implement xesam db changes
> as that will require a reindex anyhow

 Yes, before that we have all the indexer-split work to merge and stabilize.

> due to the wide changes involved I dont see much point in supporting
> multiple indexer backends

 One task less to the merge!

Regards,

Ivan