Run Digikam @ Sqlite or Mysql benefits/limitations?

[David Lyon]

I have installed Digikam 3.5.0 on Mac OS 10.9. I am experiencing  
difficulty installing Mysql server due to the following message error:

'Can't connect to local MySQL server through socket
'/opt/local/var/run/mysql5/mysqld.sock' (2)'
Check that mysqld is running and that the socket:
'/opt/local/var/run/mysql5/mysqld.sock' exists!

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?
Thanks for you consideration,
Dave
--
Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[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.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

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.

An important advantage of Sqlite (for me) is that backup of the digikam
folder automatically includes the databases, whereas MySQL needs a
separate backup, which I tend to forget, or it is not made in the same
moment as the image folders...

kind regards

Daniel


--
Daniel Bauer photographer Basel Barcelona
professional photography: http://www.daniel-bauer.com
google+: https://plus.google.com/109534388657020287386
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Marcel,

What do you think to annotate in GUI that MySQL backend still "experimental" ?

Gilles

2014/1/18 Marcel Wiesweg <[hidden email]>:

>
>
>>
>> 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.
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[maderios]

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


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> Marcel,
>
> What do you think to annotate in GUI that MySQL backend still "experimental"
> ?

I agree...as long as we dont fix the bugs...
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2014/1/19 Marcel Wiesweg <[hidden email]>:
>
>> Marcel,
>>
>> What do you think to annotate in GUI that MySQL backend still "experimental"
>> ?
>
> I agree...as long as we dont fix the bugs...

Done with commit
http://commits.kde.org/digikam/dbeccbf3594862c6b997390a5908bbe86a9c3c06

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users