https://bugs.kde.org/show_bug.cgi?id=364258
--- Comment #4 from Jens B. Benecke <jens-bugs.kde....@spamfreemail.de> --- Let me explain. Digikam 5 (beta6), when started first, did not recognize my existing albums and collections from Digikam 4.14 (on Ubuntu Linux) and just showed me a welcome and setup screen. So I logically assumed there must be a migration procedure. (This I would consider a bug - if there are previous existing collections, a new version of Digikam should just open them or offer to import them.) I found the migration option and selected my digikam4.db (the target was already preselected) and started the migration. This destroyed the digikam4.db tables as described below so subsequent starts of Digikam 4.14 wouldn't show tags etc. any more. Starting the migration might have been my mistake but a user friendly application should prevent users from doing something stupid (like starting a migration when it isn't required or possible) so I consider this a bug too. The solution is simple: upon start, just load the digikam4 config (if available) and - if required - copy it to a digikam5 config. And when a user starts the Migration task from the maintenance menu and selects database files or formats which cannot be migrated, show an appropriate error message and refuse the migration. Do you agree? -- You are receiving this mail because: You are watching all bug changes.
