UpdateSchemaFromV7ToV8 fails

Mikael Kujanpää mahead80 at nic.fi
Mon Aug 29 22:42:06 BST 2016


Maik Qualmann kirjoitti 30.08.2016 00:06:
> The log is not from last file. Please check again. I think MySQL 5.6.3 
> is
> minimum.

Bloody applications that rename files automatically without notifying 
the user. :)

I upgraded my MySql server to version 5.6.30 as I noticed that it's also 
available. This is the output with correct file and upgraded server:

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 
"/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: 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 
(albumRoot) REFERENCES AlbumRoots (id) ON DELETE CASCADE ON UPDATE 
CASCADE,\n                                        ADD UNIQUE (albumRoot, 
relativePath(190)),\n                                        ENGINE 
InnoDB;" ]
digikam.coredb: Core database: schema update to V 8 failed!
digikam.coredb: Core database: cannot process schema initialization

Thank you for your efforts for trying to solve the issue. I have to go 
to the bed for tonight (it's over midnight here in Finland), but I'm 
happy to continue tomorrow if you any ideas how to proceed.

-- 
Mikki



More information about the Digikam-users mailing list