#Debian digikam how to#

Taken from select * from Images where album not in (select Albums.id from Albums) This will show your the problems (should all be empty except the root tag): I still seem to have another issue, but probably not related to the db. After fixing those (mainly deleting some dead references) an upgrade went through.

I had the same problem due to some inconsistencies in my old db.

#Debian digikam how to#

When explicitly trying to use the db migration tool included into 5.* I end up with the error represented in the following image:Ĭan anyone help with decyphering what's going on here, respectively how to fix it? When starting digikam v5.* pointed at the 4.*-used database backend I get the following: digikam.dbengine: Loading SQL code from config file '/usr/share/digikam/database/dbconfig.xml'ĭigikam.dbengine: Checking XML version ID => expected: 3 found: 3ĭredb: Core database: running schema updateĭredb: Core database: have a structure version 7ĭredb: Core database: makeUpdates 7 to 8ĭigikam.dbengine: Failure executing query:Įrror messages: 'QMYSQL: Unable to execute query' 'Can't DROP 'Albums_AlbumRoots' check that column/key exists' 1091 2ĭigikam.dbengine: Error while executing DBAction Statement ĭredb: Core database: schema update to V 8 failed!ĭredb: Core database: cannot process schema initialization I now am facing the issue that the (mysql)database holding that labor of love appears to be giving issues when trying to upgrade to the newer data base scheme (v.8). I have ! a decade worth of tagged photographs managed with digikam and my debian stable/testing mix recently upgraded to digikam 5.*.