[Digikam-users] Changing from sqlite to mysql
Dr. Martin Senftleben
drmartinus at drmartinus.de
Sun May 25 07:11:21 BST 2014
-----BEGIN PGP SIGNED MESSAGE-----
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.
TIA
Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlOBiYUACgkQUmmuY48ByEjZKACgzjg4mSQ0oSxgKwDntJzpEGYa
M5UAoJooAcsIErymztHi9N5ok/to80aD
=dnYR
-----END PGP SIGNATURE-----
-------------- 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/20140525/9813814b/attachment.vcf>
More information about the Digikam-users
mailing list