https://bugs.kde.org/show_bug.cgi?id=372312
Bug ID: 372312 Summary: database upgrade v7 to v8 failed Product: digikam Version: 5.2.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Database-Mysql Assignee: digikam-de...@kde.org Reporter: k...@forum.titlis.org Target Milestone: --- I cannot update the database version v7 (DK 4.14) to v8 (DK 5.2). I'm using Opensuse Leap 42.2 with mariadb 10.0.27 $ digikam digikam.general: AlbumWatch use QFileSystemWatcher QFileSystemWatcher::removePaths: list is empty digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikamdb" DB Thumbs Name: "digikamthumbs" DB Face Name: "digikamfaces" Connect Options: "" Host Name: "localhost" Host port: 3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "digikamuser" Password: "XXXXXXXXX" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 7 digikam.coredb: Core database: makeUpdates 7 to 8 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "Specified key was too long; max key length is 767 bytes" 1071 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV8" ] Statement [ "ALTER TABLE Albums\n ADD CONSTRAINT Albums_AlbumRoots FOREIGN KEY (albumRoot) REFERENCES AlbumRoots (id) ON DELETE CASCADE ON UPDATE CASCADE,\n ADD UNIQUE (albumRoot, relativePath(255)),\n ENGINE InnoDB;" ] digikam.coredb: Core database: schema update to V 8 failed! digikam.coredb: Core database: cannot process schema initialization -- You are receiving this mail because: You are watching all bug changes.