More options for Note Revisions handing #258
Closed
Br0kenSilos
started this conversation in
Ideas
Replies: 2 comments 4 replies
-
@Br0kenSilos , those are really good ideas. I suggest you turn them into issues/feature requests. For the second point, I was thinking maybe we need some kind of "usage analyzer". To show how much storage is occupied in total by the DB, by notes, by revisions, by attachments and by backups. And maybe offer some ways to reduce the consumption. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would love to see some additional options for handling note revisions. For instance:
The ability to limit the number of note revisions to a specific (user selected) number and roll off the oldest revisions after that number is reached. So for instance, limit a particular branch, or note, or even the entire tree to have no more than say 3 revisions per note. When the time comes for a 4th revision, the oldest revision is then deleted in a FIFO order. The number of revisions should be flexible. So if perhaps I generally want the entire tree to have no more than 3 revisions per note, but I have one note (or branch) down in the tree somewhere that I would like to keep 10 revisions, it would be nice to be able override the 3 revisions set higher in the tree for that particular note/branch.
The option at the top of the tree (or perhaps under Options > Advanced Other (near the vacuum db option) ) to remove ALL current Revision Snapshots. This would be to simply shrink the DB and clear unused space when things are in a state that the user feels is safe to remove all snapshots.
Beta Was this translation helpful? Give feedback.
All reactions