Having the database resided in memory is good for performance but could make trouble if app session is quite long (and crash happens for some reasons). It is a good idea to dump the database to the disk periodically.
The dump itself could be performed (for example) under the following conditions:
1) Database is marked with "dump needed" (meaning database changes were made since the last dump)
2) Application is minimized (so we know that user is not making any operations with it now)
3) Application is in idle mode for at least 60 seconds (so the app itself does not perform any operations for some time)
In this case it is safe to make a dump because it will have no interference with the user and/or app actions and will not affect performance.
Seconding this, because on my machine shutting down the computer without closing RSS Guard first results in an old database state being restored, next time.
Brief description of the feature request
Having the database resided in memory is good for performance but could make trouble if app session is quite long (and crash happens for some reasons). It is a good idea to dump the database to the disk periodically.
The dump itself could be performed (for example) under the following conditions: 1) Database is marked with "dump needed" (meaning database changes were made since the last dump) 2) Application is minimized (so we know that user is not making any operations with it now) 3) Application is in idle mode for at least 60 seconds (so the app itself does not perform any operations for some time)
In this case it is safe to make a dump because it will have no interference with the user and/or app actions and will not affect performance.