https://bugs.kde.org/show_bug.cgi?id=316690
Bug ID: 316690 Summary: Database Migration by default successfully erases all data Classification: Unclassified Product: digikam Version: 2.6.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database Assignee: [hidden email] Reporter: [hidden email] By default, Database Migration window contains the same data for source and target database. After clicking Migrate button, we get clean and pristinely empty database. At the end of erasing the data, we get "Database copied successfully". I find this feature useful in some cases, but it should better me called EraseAllMySillyTags instead of Migrate, because Migrate suggests slightly different behavior ;) Reproducible: Always Steps to Reproduce: 1. Open Database Migration window. 2. Check that source and destination database are the same database. 3. Click Migrate button. Actual Results: We get clean and pristinely empty database. Expected Results: Information box, saying that source and destination database are the same, so operation has no sense. It's all about MySQL database connection. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=316690
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Database Migration by |MIGRATION : Database |default successfully erases |conversion by default |all data |successfully erases all | |data CC| |[hidden email] -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Mike Turchenkov
https://bugs.kde.org/show_bug.cgi?id=316690
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Database |Database-Migration -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Mike Turchenkov
https://bugs.kde.org/show_bug.cgi?id=316690
--- Comment #1 from [hidden email] --- This file still valid using last digiKam 5.0.0 ? Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Mike Turchenkov
https://bugs.kde.org/show_bug.cgi?id=316690
Stefano <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] --- Comment #2 from Stefano <[hidden email]> --- Yes, because the default is both SQLite as source and destination, and if you unluckily press the confirm button, it tries to migrate it... without checking that both source and destination point to the same file, ending in a voiding of the database. -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by Mike Turchenkov
https://bugs.kde.org/show_bug.cgi?id=316690
--- Comment #3 from Stefano <[hidden email]> --- It should check that the destination file does not exist, at least. -- You are receiving this mail because: You are the assignee for the bug. |
In reply to this post by Mike Turchenkov
https://bugs.kde.org/show_bug.cgi?id=316690
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[hidden email] Version|2.6.0 |5.0.0 -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |