Feature Request filed for tracking purposes:
0013790 2025-04-22 Proposed Tree Related Metadata Attributes / XML Changes (cdhorn)
Feature Request filed for tracking purposes:
0013790 2025-04-22 Proposed Tree Related Metadata Attributes / XML Changes (cdhorn)
If information about latest changes is included, perhaps a future version of Gramps could store all transactions as separate log records as well. Third parties can then check which fields were changed when, and compute their own diffs. Those will allow those third parties to merge changes into their own storage, or reduce the amount of work to perform to be for changed objects only.
You’re right, some kind of delta file format would be an interesting adaptation. (Such as: records changed since a timestamp; or, differences between 2 files … from the Import Merge addon tool.) Maybe that could be done with an set of Import/Export plugins? Or maybe a tool that parses the Database Differences addon report?
As would having an elimination in the possible recursive compressions of the XML data. Which would probably simplify processing with external tools.
Yeah so as long as the database logs all revisions/transactions, any code, including exporters, could choose to add (a subset of) this information. The database would need to use unique IDs for each revision and either details of the exact changes , or a snapshot of the object.