deleted history re-appears after sync

  • nlof

    nlof - 2011-12-31

    My database increased significantly after I attached a large file and deleting the file didn't restore the database to the smaller size. Turns out that the file is kept in "history" and even if I delete the history, after sync-ing, the entire history including this file reappears in the database.
    My setup is that I am using a trigger and webdav to auto-sync to a cloud location (myDrive) each time I save my database locally.

    Is there any way to keep the database history from reappearing if I am using this setup with auto-sync?

  • Dominik Reichl

    Dominik Reichl - 2011-12-31

    Entry histories are always merged, never deleted (except by the automatic history maintenance).

    So, in order to delete a history entry, open your two databases and delete the history entry from both manually.

    Best regards

  • nlof

    nlof - 2011-12-31

    Thanks Dominik. I ended up saving the file locally as well as uploading it to the cloud without syncing so I assume it is fixed.

    What's automatic history maintenance btw? The rule to limit history to X number of entries / Y number of kB ?

  • nlof

    nlof - 2011-12-31

    Oh and I need to remember to copy the database now to all my other computers / locations without syncing  to avoid re-appearance of the history :) lol

  • Paul

    Paul - 2011-12-31

    File > Database Settings > Advanced

    cheers, Paul

  • David Pierson

    David Pierson - 2014-05-02

    Thanks for the explanation, Dominik.

    I have five devices, so it is a bit tedious. Is there a fix for this in the pipeline?

  • wellread1

    wellread1 - 2014-05-02
    • To reduce the history size in the entire database, adjust either "Limit number of history items per entry" or "Limit history size per entry (MB)" in "File>Database Settings...>Advance(tab)'

    • To remove the history from selected entries choose 'Edit>Duplicate Entry' and deselect the 'Copy History' check box in the 'Duplication Options' dialog. Finally delete the original entries and synchronize. CAUTION: Do not check 'Replace user names and passwords by references'

    Last edit: wellread1 2014-05-02
  • David Pierson

    David Pierson - 2014-08-08

    Hi wellread1,
    Thank you for replying. This is the scenario:
    - find an entry with some old history
    - delete some of those old history
    - sync
    All of the deleted history has returned. However, having tried to think up the logic that would be necessary in the history-merge in sync, to solve this while not losing anything that could be wanted, I've not thought of a solution yet. If I do ...

  • wellread1

    wellread1 - 2014-08-08

    The History depth is set for the entire database in 'File>Database Settings>Advanced(tab)'. During a sync, an entry's history will be restored to a depth that equals the combined unique history entries of the active and target databases, up to the maximum depth set in database settings for the active database.

    To manage history depth for the entire database set the 'limit number of history items per entry' and 'Limit history size per entry (MB)' in Database settings.

    The easiest way to remove the history for a single entry is to duplicate the entry without a history (e.g. Right click on the entry, select Duplicate, un-check copy History). Then delete the original entry. At the next sync the original entry will be deleted from both databases and the duplicate (without a history) will be replicated in both databases. Otherwise you need to trim an entry's history to the desired depth individually in every copy of the database before syncing.

    See also

    Last edit: wellread1 2014-08-09

Log in to post a comment.