[Digikam-users] Run Digikam @ Sqlite or Mysql benefits/limitations?

maderios maderios at gmail.com
Sat Jan 18 16:45:04 GMT 2014


On 01/18/2014 01:19 PM, Daniel Bauer wrote:
> Am 18.01.2014 12:37, schrieb Marcel Wiesweg:
>
>>> I have discovered that I can run Digikan with "Type" setting of
>>> Sqlite in
>>> the database setting. Is the performance of Digikam diminished  or its
>>> integrity compromised by running it with Sqlite?
>>
>> SQLite is currently the standard option and the one which most of the
>> active
>> developers are using. The MySQL backend has bugs.
>> In principle, MySQL can be more performant than Sqlite as regards
>> concurrent
>> write operations. For reading, SQLite is very fast.
>
> I tried mysql some dk versions back, but it did not convince me (that
> might have changed by now, don't know) so I returned to Sqlite.
>
DK 2.6 (debian stable version) works well with mysql extern server, 
except some tags minor bugs. For me (30 000 pictures) , sqlite is 
unusable : much too slow.
I periodically  backup mysql db with mydumper.

-- 
Maderios





More information about the Digikam-users mailing list