The problem is that this syntax is obsolete since mysql 5.7. From mysql documentation https://dev.mysql.com/doc/refman/5.6/en/alter-table.html:
> As of MySQL 5.6.17, the IGNORE clause is deprecated and its use generates a > warning. IGNORE is removed in MySQL 5.7.
the required console output:
digikam.coredb: Core database: makeUpdates 8 to 9
digikam.dbengine: Failure executing query:
Error messages: "QMYSQL: Unable to execute query" "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IGNORE TABLE AlbumRoots\n ADD UNIQUE (iden' at line 1" 1064 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV9" ] Statement [ "ALTER IGNORE TABLE AlbumRoots\n ADD UNIQUE (identifier(127), specificPath(128)),\n ENGINE InnoDB;" ]
digikam.coredb: Core database: schema update to V 9 failed!
digikam.coredb: Core database: cannot process schema initialization
KMemoryInfo: Platform identified : "LINUX"
KMemoryInfo: TotalRam: 16748412928
digikam.general: Allowing a cache size of 200 MB
QThreadStorage: Thread 0x7ff8652ab100 exited after QThreadStorage 11 destroyed
Created attachment 109865 [details]
Replace the dbconfig.xml under /usr/share/digikam/database/ with this one. If the entries in the database is in a clean state, the schema update should work fine with MySQL-5.7.
Git commit 5893fde69518d70904d2b96e13800c7432b4e4c4 by Maik Qualmann.
Committed on 15/01/2018 at 19:24.
Pushed by mqualmann into branch 'master'.
fix schema update from V7/8 to V9 with temporary tables
Related: bug 388867, bug 388824
M +4 -2 NEWS
M +124 -30 data/database/dbconfig.xml.cmake.in
Created attachment 109887 [details]
Fix for digiKam-5.8.0: Replace the dbconfig.xml with this one.
File path Windows:
File path Linux:
Created attachment 109894 [details]
Small updated dbconfig.xml.
Created attachment 109981 [details]
thx that worked
Created attachment 109997 [details]
*** Bug 389677 has been marked as a duplicate of this bug. ***
*** Bug 391340 has been marked as a duplicate of this bug. ***
*** Bug 392179 has been marked as a duplicate of this bug. ***
*** Bug 392189 has been marked as a duplicate of this bug. ***