| Summary: | Online doc: add annotation about the migrating database do not copy all database files at new place. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | hardy.public |
| Component: | Documentation | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot of database comparison | ||
|
Description
hardy.public
2017-12-20 12:02:56 UTC
Hi Hardy and happy new year, Please check with digiKam 7.5.0 pre-release windows installer available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Created attachment 145337 [details]
Screenshot of database comparison
Happy New Year!
I think the behaviour is the same. Only digikam4.db is truly copied, the other .db files are basically empty.
Same issue with Database Migration feature. With LHS and RHS both SQlite only digikam4.db is recreated on the RHS. The others are missing. This is intended, it is better to rebuild the other databases. Maik (In reply to Maik Qualmann from comment #4) > This is intended, it is better to rebuild the other databases. > > Maik If so then there is no issue but the Database Migration dialogue therefore needs different text. The text talks about plural databases: properties, thumbnails and faces. The curious end user would rightly expect three .db files at the end of the migration process. If your intention is that only one database is migrated and the others are regenerated when required then I think that needs clarifying in the dialogue. Maik, Another entry to patch the online documentation abou tthe DB migration tool. Gilles |