No subject

sqlite needs to write twice to disk on each transaction, once for the journal,
and then again for the actual data. It is not cached like in a real SQL server,
so speed gains in reading and writing should not be visible I guess.
Who knows, it might be even slower, but this can only be seen when we actually
use it.
Sure it could be packed into one big transaction, but I guess this will waste
memory and kill performance.

As I said before, I would think some hybrid would be better, store all remote
thumbs in the database, the local ones in the file system.
But this makes code more complicated again.

Andi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.