UpdateSchemaFromV7ToV8 fails

Mikael Kujanpää mahead80 at nic.fi
Mon Aug 29 20:17:42 BST 2016

Maik Qualmann kirjoitti 29.08.2016 22:07:
> Please can you try this attached dbconfig.xml file?

Thanks for your file. Unfortunately, no luck:

mkujanpa at earth:~$ digikam
digikam.general: AlbumWatch use QFileSystemWatcher
QFileSystemWatcher::removePaths: list is empty
digikam.general: Database Parameters:
    Type:                     "QMYSQL"
    DB Core Name:             "digikamdb"
    DB Thumbs Name:           "digikamthumbdb"
    DB Face Name:             "digikamfacedb"
    Connect Options:          ""
    Host Name:                "neptunus"
    Host port:                3306
    Internal Server:          false
    Internal Server Path:     ""
    Internal Server Serv Cmd: ""
    Internal Server Init Cmd: ""
    Username:                 "digikam"
    Password:                 "XXXXXXXXX"

digikam.dbengine: Loading SQL code from config file 
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: Kyselyn suorittaminen epäonnistui" "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 
CASCADE,\n                                        ADD UNIQUE (albumRoot, 
relativePath(250)),\n                                        ENGINE 
InnoDB;" ]
digikam.coredb: Core database: schema update to V 8 failed!
digikam.coredb: Core database: cannot process schema initialization

At least it can be seen that new file was in use, because now it reads 
"relativePath(250)" in the middle of there.


More information about the Digikam-users mailing list