[Digikam-users] Changing from sqlite to mysql (was: Re: dk 4.0 problems with cropping)

Dr. Martin Senftleben drmartinus at drmartinus.de
Sat May 24 06:26:15 BST 2014

Hash: SHA1

Hi Gilles and all others,

Am 23.05.2014 22:30, schrieb Gilles Caulier:
> fixed in current implementation. It will be published in 4.1.0

thanks! Good that you could find the cause.

I still have problems with the stability of digikam (in fact, this is
a continuous problem). Every now and then it crashes (yesterday four
times), often when there is no really heavy task is at hand, like when
I click on an image to see a larger version of it, or when I want to
open the editor.

Now I was wondering if this could be because of the size of my
collection. I'm using sqlite, that seemed sufficient when I started.
Now I read that it's good for collections with up to 100.000 images,
beyond that it would be better to use mySQL.
I have about 280.000 files in my collection, while I'm not sure how
many sidecar files are in this collection. I don't know if this would
be relevant, but let's estimate some 20.000 images have sidecar files,
so it still comes to more than double as many images as recommended
for sqlite. So I would like to change to mySQL as database in the hope
this will improve things. But how to go about it without losing any
date like tags, descriptions etc.?


Version: GnuPG v1

-------------- next part --------------
A non-text attachment was scrubbed...
Name: drmartinus.vcf
Type: text/x-vcard
Size: 370 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20140524/dedec3aa/attachment.vcf>

More information about the Digikam-users mailing list