Re: [Tracker] Sqlite now default in cvs (mysql backend wont compile yet!)

[Anders Aagaard <aagaande gmail com>]

Jamie McCracken wrote:
> I have ben spending the last few weeks adding in the sqlite/qdbm 
> complete with indexer and parser.
>
> This is now basically functional in cvs.
>
> Stuff that wont work is :
>
> 1) RDF query
> 2) only tracker-search (no location or mime yet in nautilus)
> 3) exact phrase search
>
> I have not updated the mysql backend yet so it wont compile at the 
> moment so you are *forced* to try out the sqlite one :)
>
> (I figure unless theres a strong reason to have the inferior mysql 
> version we can phase it out?)
>
> New features with new indexer are:
>
> 1) differential indexing for faster updates
> 2) stemming so searches for "penguin" will match against "penguins"
> 3) Bzip compression of full text so it has much smaller footprint in the 
> sqlite db

Why chose bzip?  Considering it's performance I'd rather choose gzip, or
if your desperate for space 7zip (there are open linux implementations,
p7zip or something like that).

> 4) high performance qdbm file based hash table for search thats fully 
> scalabale up to many GBs on indexes without significant speed loss.
>
>
> to compile you will need bzip dev stuff, qdbm dev stufff as well as sqlite3
>
>
> Databases are now in Home/.Tracker/databases.
>
> "data" file can be viewed with sqlite3 command line program
>
> "Files" file can be viewed with dpmgr command line program (to optimise 
> space of this file the following should be entered after indexing :
>
> dpmgr optimize Files
>
> (we will do this automatically in future after every 10,000 updates or so)
>
> Please test and report any bugs.