Optional file storage for data persistence #881
+86
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The persistence topic has been already addressed in issues #350 and #406. We have another use case where the tests of the command line interface require saving the database and making it available across several processes. Therefore, some temporary file storage is necessary.
This can be accomplished by a small extension of the classes in
store.py
. The file store is not intended to keep database state instantly on disk. Rather the database is eventually dumped to a file just before theServerStore
object is destroyed.It is a work in progress: TODO: a transparent method to pass the option to use a database file with a database file path. This can be accomplished e.g. by using an environment variable.The persistence is activated either by setting the environment variable MONGOMOCK_SERVERSTORE_FILE to a non-empty JSON file (initialized with '{}'):
export MONGOMOCK_SERVERSTORE_FILE=/full/path/to/mongomock_file.json
or create a custom
ServerStore
object by passing thefilename
keyword argument: