| Summary: | Failed to update the database schema from version 7 to version 8. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Vlado Plaga <rechner> |
| Component: | Database-Migration | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version: | 5.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.2.0 | |
| Sentry Crash Report: | |||
| Attachments: | console output | ||
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 *** This bug has been marked as a duplicate of bug 379987 *** Fixed with #379987 and not reproducible with 6.2.0 |
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.