[Digikam-devel] [digikam] [Bug 341772] Re-read metadata when image file timestamp has changed [patch]

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=341772

--- Comment #10 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
This is a very sensitive area. The current behavior has been conservative all
these years:
You are not forced to have your db in sync with your metadata. You can update
the metadata in the database and not write the change to the image. You can
switch off writing to RAW images. There may be image formats which contain
metadata but for which writing is not supported or experimental. Plus
constellations that we did not think of. 
Against this background the full re-scan has been a manual operation.

If now any change in the file's modification date, which is done so easily,
will cause a full re-scan, we change behavior which was constant over many
years. I see many bugs reports and annoyed users.

The change is completely valid for your setup, but for me it must come with a
setup option to enable it, and must be disabled by default.

-- 
You are receiving this mail because:
You are the assignee for the bug.