Bug 381386 - Failed to update the database schema from version 7 to version 8.
Summary: Failed to update the database schema from version 7 to version 8.
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Migration (show other bugs)
Version: 5.6.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-19 05:05 UTC by Vlado Plaga
Modified: 2019-07-14 12:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.2.0
Sentry Crash Report:


Attachments
console output (5.83 KB, text/plain)
2017-06-19 05:05 UTC, Vlado Plaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vlado Plaga 2017-06-19 05:05:28 UTC
Created attachment 106164 [details]
console output

I had Digikam (4.4 and earlier) use an external MySQL database (though marked experimental)... and now I'm facing update problems. It does not work with DigiKam 5.4 (from Kubuntu 17.04), and the problem seems to be the same with DigiKam 5.6, started from digikam-5.6.0-01-x86-64.appimage.

Actually the AppImage seemed to introduce a new problem: it is trying to connect to MySQL through /var/lib/mysql/mysql.sock, although on Ubuntu the socket is under /var/run/mysqld/mysqld.sock - I changed it for testing purposes.

I tried manual DB fixes also, as described in #373605. The commands found 23 problematic entries in 4 tables.

I can still start DigiKam 4.4 under Debian (old stable), but in there the Database Migration dialogue does not work... so I wonder how I'm going to get my database converted to the current DigiKam standard.
Comment 1 caulier.gilles 2017-12-13 22:36:41 UTC
With next 5.8.0 release Mysql support have been well improved and a lots of bugs fixed.

Please test with pre release 5.8.0 bundles that we provide and give us a feedback

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 2 Maik Qualmann 2017-12-19 07:43:53 UTC

*** This bug has been marked as a duplicate of bug 379987 ***
Comment 3 caulier.gilles 2019-07-14 12:50:29 UTC
Fixed with #379987 and not reproducible with 6.2.0