Previous versions of the MySQL digikam database schema did not enforce referential integrity and hence can have inaccessible orphan rows in the database. During migration digikam needs to take care to ignore these rows so that the migration can continue without manual cleanup of the original MySQL database first. I have a patch against current git. This has been tested using the 5.7.0 and 5.6.0 pre-release app images during a migration of my digikam 4.x MySQL data to 5.x digikam.
Created attachment 106864 [details] Ignore orphan rows in MySQL migration This can be tested on an existing digikam installation by replacing /usr/share/digikam/database/dbconfig.xml with a patched copy and then restarting digikam.
Git commit a791ee52e031403067ca5dea709c86f5f61f2371 by Maik Qualmann. Committed on 04/08/2017 at 19:41. Pushed by mqualmann into branch 'master'. apply patch #106864 from Richard Mortimer to ignore orphan rows in MySQL migration FIXED-IN: 5.7.0 M +4 -3 NEWS M +40 -16 data/database/dbconfig.xml.cmake.in https://commits.kde.org/digikam/a791ee52e031403067ca5dea709c86f5f61f2371
Git commit fc0496a56d29992c3a97404c1dc0246a2d57e941 by Ahmed Fathi Shaban, on behalf of Maik Qualmann. Committed on 06/08/2017 at 23:14. Pushed by ahmedfathy into branch 'gsoc17-dlna'. apply patch #106864 from Richard Mortimer to ignore orphan rows in MySQL migration FIXED-IN: 5.7.0 M +4 -3 NEWS M +40 -16 data/database/dbconfig.xml.cmake.in https://commits.kde.org/digikam/fc0496a56d29992c3a97404c1dc0246a2d57e941