Bug 388070 - Online doc: add annotation about the migrating database do not copy all database files at new place.
Summary: Online doc: add annotation about the migrating database do not copy all datab...
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Documentation (other bugs)
Version First Reported In: 7.5.0
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-20 12:02 UTC by hardy.public
Modified: 2023-10-23 09:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of database comparison (21.40 KB, image/png)
2022-01-11 19:01 UTC, hardy.public
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hardy.public 2017-12-20 12:02:56 UTC
When selecting a new path for the database, the "Copy Current Database" button does the following:

(1) Only copies across digikam4.db and thumbnails-digikam.db. recognition.db is not copied.

(2) thumbnails-digikam.db in the new location contains a minimum file-size 52kb (empty?) and therefore all thumbs displayed are green mountain placeholders.

(3) digiKam does not attempt to regenerate thumbs until digiKam is restarted.

Expected Behaviour:
All three db files copied to new location, digiKam reloads new db files. Thumbnails readily available, no need to regenerate.
Comment 1 caulier.gilles 2022-01-10 10:21:17 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
Comment 2 hardy.public 2022-01-11 19:01:27 UTC
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.
Comment 3 hardy.public 2022-01-11 19:33:20 UTC
Same issue with Database Migration feature. With LHS and RHS both SQlite only digikam4.db is recreated on the RHS. The others are missing.
Comment 4 Maik Qualmann 2022-01-11 19:47:24 UTC
This is intended, it is better to rebuild the other databases.

Maik
Comment 5 hardy.public 2022-01-12 18:30:06 UTC
(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.
Comment 6 caulier.gilles 2023-10-15 12:48:06 UTC
Maik,

Another entry to patch the online documentation abou tthe DB migration tool.

Gilles