[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||6.0.0 CC|

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 Kusi changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 --- Comment #5 from Kusi --- I solved the issue by export/import of the database. That is probably good enough also for other users with this issue. I'm closing this bugreport -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 --- Comment #4 from caulier.gil...@gmail.com --- Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle available here : https://files.kde.org/digikam/ -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 --- Comment #3 from Maik Qualmann --- No, the image ids do not change. Presumably, many orphaned will no longer exist after the migration. The database will certainly be smaller, but nothing should be lost. Maik -- You are

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 --- Comment #2 from Kusi --- my db is over 12 years old I guess. Looking at the mysql dump, there's indeed alot of garbage (many unneeded constraints and indexes) compared to how a new db looks like. Digikam with db v9 is now

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

https://bugs.kde.org/show_bug.cgi?id=394291 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com