[Digikam-users] Changing from sqlite to mysql

maderios maderios at gmail.com
Sun May 25 13:57:31 BST 2014

On 05/25/2014 08:11 AM, Dr. Martin Senftleben wrote:
> Hash: SHA1
> Hi,
> Am 24.05.2014 07:43, schrieb Gilles Caulier:
>> Sqlite code has introduced recently an hazardous instability. It's
>> a UPSTREAM problem reported a lots of time in bugzilla here :
>> https://bugs.kde.org/show_bug.cgi?id=329697
>> THe solution is to update sqlite3 AND QtSqlite plugin. This last
>> one is used in fact. digiKam do not use Sqlite3 library directly.
> And how do I go about it? There's no update in the repository. Is
> there a way to get the update without having to compile the stuff?
> Still there is the question how to speed things up. When managing
> files, it takes awfully long (moving, deleting or copying images for
> instance), if it works. If mysql is no option, what then? With about
> 250.000 files to manage sqlite seems to reach its limits.
You may use Mysql but it's considered as experimental.
Mysql works for me with xmp tags. Be careful, experiment first in a 
special account/user only used for testing. If you dot it, always sync 
from images tags to database and never from database to images (you may 
loose yours tags). If it doesn't work, you can return to sqlite.


More information about the Digikam-users mailing list