You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somebody might volunteer for coding the append mode, where output is written to a file (instead of stdout as it is now) and new entries are compared with existing ones.
In append mode, only non-existing entries are appended. This is helpful when Firefox SQLite DB is a sliding window and Memacs output file should cover the whole story.
The text was updated successfully, but these errors were encountered:
So the idea is to parse the old orgmode file? Because one could also just store all entries in a database/pickled python dictionary(stored in the orgmode folder or the memacs folder) and then append the new entries to that but rewrite the orgmode file every time.
That way one would not have to write/use a parser to get the data and the org file is not vulnerable to change. On the other hand one would need to take care of the database/dictionary instead of the orgfile.
So far, the append mode of existing modules is using the "parse the existing/old orgmode result files and take a look on the IDs"-approach.
I can't remember the discussion when we decided to go that way. Most probably it was because we wanted to avoid any state-keeping outside of source and target files. With these DBs you have to worry about inconsistencies between: DB and existing orgmode files, DB within itself (data corruption,...).
Since we had those unique IDs (hashes from data), the comparison of IDs was more elegant to us, I guess. The git-principle: data = hash = checksum = identifier.
Somebody might volunteer for coding the append mode, where output is written to a file (instead of stdout as it is now) and new entries are compared with existing ones.
In append mode, only non-existing entries are appended. This is helpful when Firefox SQLite DB is a sliding window and Memacs output file should cover the whole story.
The text was updated successfully, but these errors were encountered: