Improve FAQ: Can the database be saved automatically?

[Franzi]

Hi,

today I stumbled upon the topic of auto save the database as explained here (it's also in the attachment):
https://keepass.info/help/kb/faq.html#autosave

The last bullet point states the following:
“Periodic.
If you want the database to be saved periodically, you can create a trigger for this (with the event 'Time - Periodic'). This approach is for experts; for most users, the two options above are recommended instead.”

At the beginning I thought I have to develop my own trigger in order to auto save my database with a time delay when a database change occurs. So, I read the page about triggers and tried to develop my own trigger.
But then I discovered that there is a trigger example page. And on this page, there is already an example of the triggers I needed (save automatically when a database change occurs with a time delay of 120 seconds). It’s here:
https://keepass.info/help/kb/trigger_examples.html#autosave

The time delayed auto save is superior to the predefined option “After modifying an entry” in the auto save FAQ, because sometimes you would like to do multiple database changes one after another, which is a problem with “After modifying an entry”, because you have to wait after each database change some time until the save operation is finished in order to do the rest of the database changes.

My wish is to add another bullet point in the auto save FAQ (https://keepass.info/help/kb/faq.html#autosave) that informs about the autosave trigger example (https://keepass.info/help/kb/trigger_examples.html#autosave).

And you should also mention that auto save is executed with a time delay in the trigger example page (https://keepass.info/help/kb/trigger_examples.html#autosave). Currently, this is omitted, I quote: “These triggers make KeePass save automatically when a database change occurs.”

If it is not too much work I would also endorse it if this delayed auto save would be an own option in the advanced tab, you could set a field with spinners where you can choose how many seconds you want to delay the autosave in the existing option “Automatically save after modifying an entry using the entry editing dialog”.

Cheers

[Paul]

The trigger examples are just that, examples of what you can do with a trigger. Users are expected to have some understanding of the process that the trigger performs and if something is not clear you can always ask here.

Auto-save after x period is not a great idea IMO. If you set the delay too long you may lose the changes if the machine is shut down etc.
There is no downside to saving immediately, unless your save is on a slow link, in which case you should save locally and then sync to prevent comms issues stopping the save.

If you are worried about multiple saves damaging the database, install one of the auto-backup plug-ins.

cheers, Paul

[Franzi]

And while it is great to have this trigger example, it depends on finding, understanding it (or asking about it). Let's be honest, how likely is that? There are many people out there that are users of keepass, but not necessarily programmers, etc. Allow also these users that are total beginners with no real experience in programming etc. to use this trigger example as easy as possible.
I am sure this trigger example has been used and modified many times, but the problem with the current situation is that this trigger example has not been given back to the whole community, because it is not user friendly enough for most of the keepass users (see also: https://sourceforge.net/p/keepass/discussion/329220/thread/9eaa1b2810/#addf). This is not a very sustainable approach, I'd say.
So, in the long run, useful trigger examples should become features one day, in my opinion.

Regarding the answer:

There is no downside to saving immediately, unless your save is on a slow link, in which case you should save locally and then sync to prevent comms issues stopping the save.`

I cannot reproduce this statement, I save my database locally and saving keepass takes 13 seconds (13 seconds in which I cannot use the program, I have stopped the time).

[Paul]

saving keepass takes 13 seconds

That is an extraordinarily long time for a save.
Have you set an extreme number of encryption rounds?
Is your database 10s of MB?

cheers, Paul

[Franzi]

I don't see how that's relevant to this discussion. Am I really the only person who thinks that the FAQ could be improved by beeing more specific?

[Horst]

Its so simple, install the KPSimpleBackup plugin
and your database is saved automatically after every change.