https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #12 from Kusi <k...@forum.titlis.org> --- I've added my dbconfig.xml with which I was successful. In addition to the modified dbconfig.xml, the following changes to the db were needed - Since I have many Umlaute, accents etc in my db, I first had to fix the encoding. You have the utf encoding in your dbconfig.xml, but for unknown reasons I had to do that explicitly first before running DK. I assume it comes with the ENGINE change. ALTER TABLE digikamdb.Albums DEFAULT CHARSET=utf8; ALTER TABLE digikamdb.Images DEFAULT CHARSET=utf8; - During creation of the Albums_AlbumRoots constraint, you limit the column "relativePath" to 255 chars, but that didn't do the trick (neither did it for other users on digikam-user mailing list, as you remember). I don't know why (again I assume its because of the ENGINE change to InnoDB), though. I had to change the datatype from LONGTEXT to VARCHAR(255) in the ALTER command of the v7 to v8 upgrade statement For me, the issue is resolved, but I don't think the solution to my issues is applicable for everybody. If needed, you can have my db to experiment (in an anonymized form), let me know. Am I the only one with plenty of FK constraint violations? If needed by someone, I have a (risky) script which resolves them. -- You are receiving this mail because: You are watching all bug changes.