-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to back up only changed notebooks? #72
Comments
Yes, this is the desired behavior from This would only be possible if each note is exported individually, but then a complete import would no longer be possible and you have to import every note for its self, and all internal links would be lost and the folder structures. |
What I mean is that let's say I've got 20 notebooks and I make a backup. The initial backup contains all of those 20 notebooks. Then I edit just a single note in one of the notebooks. Then I do yet another backup. The new backup still contains all 20 notebooks, even though in reality the "change" was in a single note in only one of those notebooks. Is it still required to always back up all notebooks in such a situation (instead of just the one which contains the edited note)? |
Yes it`s required to always back up all notebooks. Each note gets a new ID during the import and therefore duplicates are created and the links between the notes are lost The following will happen when not: You have the following:
The |
I see… Thank you for the explanation! I originally enabled the per-notebook backup to save space, but this means that there is basically no difference in size when compared to a single JEX backup, right? |
Correct, the option is only that a full export is created when some note, notebook, tag or resource has changed. |
Please forgive me if the question has been asked before, but would it be difficult to implement an option to back up only changed notebooks? Currently, when using the "only on change" backup type, the plugin still exports all notebooks to JEX even if only some of them have actually changed since the last backup.
The reason for this is to reduce the backup size.
The text was updated successfully, but these errors were encountered: