Tracker in Edgy?

[Jamie McCracken]

John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> Jamie McCracken wrote:
>> David Nielsen wrote:
>>> tor, 29 06 2006 kl. 16:14 +0100, skrev Jamie McCracken:
>>>
>>>> Tracker will be better integrated in Gnome in the near future with
>>>> Rhythmbox (using tracker to find music files and smart playlists) and
>>>> Epiphany (using Tracker's first class bookmarks/history objects)
>>>> integrating with it
>>> That sounds ace, now if it could index tomboy notes as well it would
>>> really make my day.
>> Its on my to do list.
>>
>> The optimal solution is to get Tomboy (at least optionally) to store its
>> notes in tracker's db (anything in the DB is auto indexed without the
>> need to write any code!) rather than indexing externally like Beagle does.
>>
> 
> Storing everything in one dbfile is a bad idea.  When that dbfile dies,
> everything dies with it.
> 
> I would rather be able to track external objects like .desktop files
> than store them in one big database.

well you will have both with tracker's database as a cache

> 
>> This is even more important for bigger things like emails as if they
>> were stored in tracker's db it would save tons of disk space. (1GB of
>> emails would take about 1.2GB in tracker's database (the index size is
>> about 20%-25% of the size) compared to 1GB mbox file + 1GB of text +
>> 0.2GB of indexes if done externally)
> 
> I've never corrupted an mbox file but it could happen.  I always thought
> a BDB or Sqlite would have been better but those can get ripped too.

the embedded mysql has automatic repair and recovery - it is  a lot 
safer than either of those. Most people dont know how to repair text 
based stores like mbox so the fact its text based is academic and any 
self healing system would be the best choice.

You will never get corruption on journalised file systems from power 
cuts as all updates on them are atomic. (the windows registry fiasco 
where it got corrupted if power was lost would never occur on a proper 
journalised FS)

also mysql has an excellent reputation with regards to the integrity of 
its databases.

Any risk to data is pretty much negligible (IMO).

-- 
Mr Jamie McCracken
http://jamiemcc.livejournal.com/