https://bugs.kde.org/show_bug.cgi?id=451524
Bug ID: 451524
Summary: synchronizing metadata from database to files should
not modify files whose metadata have not changed
Product: digikam
Version: 7.4.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Maintenance-Metadata
Assignee: digikam-bugs-n...@kde.org
Reporter: j...@kamens.us
Target Milestone: ---
When you tell the maintenance tool to synchronize metadata from the database to
the image files, it writes semantically meaningless changes to the metadata in
some cases, e.g., changing the order of names in the "Subject" field, and
updates the timestamp on every single image file even if the file is 100%
identical in content, i.e., no changes were made to the metadata.
This is terrible behavior, for three reasons: (1) it takes MUCH longer to write
every single file when most aren't actually modified in any meaningful way; (2)
every time you write to a file there's a chance of corruption, so unnecessary
writes should be avoided; (3) it causes every single file in the collection to
be backed up again, consuming bandwidth and backup space and creating cruft in
the backup for those of us who keep multiple revisions of backed-up files.
Since I assume that the digiKam is writing the metadata into a temporary file
and then replacing the original file with the temporary one (if not, it should
definitely be doing that!), it should actually check while writing the metadata
whether anything meaningful was actually changed (keeping in mind that some
metadata should be compared without regard to sort order), and if not, then
just delete the temporary file rather than replacing the original with it.
--
You are receiving this mail because:
You are watching all bug changes.
