Bug 434101 - Image Editor to save changes in DB to keep history
Summary: Image Editor to save changes in DB to keep history
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: ImageEditor-Versioning (other bugs)
Version First Reported In: 7.1.0
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-07 11:06 UTC by info
Modified: 2025-12-25 10:54 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description info 2021-03-07 11:06:44 UTC 
Can the image editor please save the changes in the DB and NOT force the user to create new files where the change history is lost after the safe.

Having the chance to see what was done to get to the result helps to do this to other images later, when needed.

So a more, Lightroom approach.
Comment 1 caulier.gilles 2025-12-20 20:35:22 UTC 
Maik,

I'm not sure to understand this entry. By save in the DB, user want mean save the image data ? It's an on scence for me

Gilles
Comment 2 Maik Qualmann 2025-12-20 21:12:12 UTC 
Hi Gilles,

I don't really understand it either. I would guess that it refers to the image editing history.

Maik
Comment 3 caulier.gilles 2025-12-21 05:09:13 UTC 
The versioning store the history of filters used in image editor in the database and duplicate the history in the file metadata as XML data.

Gilles Caulier