Summary: | database migration sets wrong parent ids for tags | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | beaaeecffmiqwryxcmbw2ta2cukc4 |
Component: | Database-Migration | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 5.4.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/digikam/9a17c743ea9a41c1ef050b08517343813ef6a9f4 | Version Fixed In: | 5.8.0 |
Sentry Crash Report: |
Description
beaaeecffmiqwryxcmbw2ta2cukc4
2016-09-19 22:07:37 UTC
Tge migration from 5 to 8 has no chance to be done properly. The Mysql current database Schema has changed to much. Tips : From old database backup and previous version, store digiKam properties in files metadata and create new database with 5.x from scratch. Gilles Caulier Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier Yes, it's still broken, all parent ids are set to "-1". Did a migration from version 8 (digikam-5.3.0-2.fc24.x86_64) to 8 (digikam-5.4.0-01-x86-64.appimage). Git commit 9a17c743ea9a41c1ef050b08517343813ef6a9f4 by Maik Qualmann. Committed on 25/11/2017 at 22:02. Pushed by mqualmann into branch 'master'. update DB to v9 and fix migration from SQLite to MySQL Related: bug 378838, bug 350574, bug 325654 FIXED-IN: 5.8.0 M +5 -1 NEWS M +129 -97 data/database/dbconfig.xml.cmake.in M +1 -1 data/database/mysql-global.conf M +1 -20 libs/database/coredb/coredbcopymanager.cpp M +5 -2 libs/database/coredb/coredbschemaupdater.cpp https://commits.kde.org/digikam/9a17c743ea9a41c1ef050b08517343813ef6a9f4 |