[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #17 from Kristian Karl --- But then all is fine! -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #16 from Maik Qualmann --- This is an old behavior that metadata is only updated and added to the DB. For users who only store the metadata in the DB and not in the images/sidecar. In digiKam-6.0.0, there is a new option to enable "Clean-up

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #15 from Kristian Karl --- Created attachment 114931 --> https://bugs.kde.org/attachment.cgi?id=114931=edit Old metadata remains after file is re-scanned Hi Maik, I think your solution looks really good. I tested it, and the re-scanning

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 Maik Qualmann changed: What|Removed |Added Attachment #114391|0 |1 is obsolete|

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #13 from Eric --- (In reply to Maik Qualmann from comment #12) > I do not know if this is your suggestion. I believe you and I are saying the same thing: if digiKam changes either the image file or its sidecar (or both), update the

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #12 from Maik Qualmann --- I do not know if this is your suggestion. But save the current date in the DB, whether image or sidecare is the solution. Karl's solution does not work with third-party programs. Now we can check if there is a new

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 Eric changed: What|Removed |Added CC||pub08-...@davor.org --- Comment #11 from Eric --- How

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #10 from Maik Qualmann --- (In reply to caulier.gilles from comment #9) > Maik, > > Yes, this last idea is sound better. So the file modification time-stamp in > DB is a resume of item or xmp sidecar change. One entry in DB for both. >

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #9 from caulier.gil...@gmail.com --- Maik, Yes, this last idea is sound better. So the file modification time-stamp in DB is a resume of item or xmp sidecar change. One entry in DB for both. Right ? What's happen if image change and not

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #8 from Maik Qualmann --- Yes, Gilles. But I have another idea. If writing is only activated to sidecar, the modification date of the sidecar file will be written to the DB instead of the image. That would save us any changes to the DB.

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #7 from caulier.gil...@gmail.com --- Maik, Your last Q is for me ??? Gilles -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #5 from Kristian Karl --- If you don't mind. I can try to have a go at suggesting a new patch, where the modification timestamp of the sidecar file is stored in the database (as Maik suggested) and used. I guess it will take me a week to

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #4 from Kristian Karl --- I'm using my patch as a work-around for now. Sync'd metadata is a bit more important to me, than the significant drawback of increased backup times. -- You are receiving this mail because: You are watching all

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #6 from Maik Qualmann --- Gilles, how do you see that? Add additional modification date of the sidecar file in the DB? Or adjust the file modification date of the image file? I do not see another solution. Maik -- You are receiving this

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 --- Comment #2 from Kristian Karl --- I went for a solution that was easy enough to implement. I'm not sure if any data for sidecar files like, hash, size or modification times are saved to the database? I agree that the changing timestamps on files

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

https://bugs.kde.org/show_bug.cgi?id=397340 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Update image file |Update image file