| Summary: | Rebuilding thumbnails does not really rebuild thumbnails, no change in db size | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | testvonmir |
| Component: | Maintenance-Thumbs | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.5.0 | |
| Sentry Crash Report: | |||
|
Description
testvonmir
2022-01-07 17:58:33 UTC
It is completely normal. The thumbnails will be recreated and stored in the database. It is common that this does not reduce the size of a database because of performance. In the maintenance tool you can clean up the database of old entries and run a vacuum. Now the database is also getting smaller. We have already improved the process in digiKam-7.5.0 and fixed bugs. Maik Okay, thanks for explaining. But when rebuilding thumbs after switching to high-res thumbs, I should notice an increase in data base size (as it also did when after it rebuilt the thumbs when I deleted the database file), correct? This did not work for me - is it already fixed, too or can't it be reproduced and was just a "temporary glitch" for me? Regards Normally, thumbnails are stored in the database with 256px. If you activate high-resolution thumbnails in the digiKam setup, thumbnails are recalculated with 512px, the database should be larger, depending on how big the vacuum of the DB is. If you have a 4K desktop resolution, thumbnails can even be created with 1024px. Maik |