-
Notifications
You must be signed in to change notification settings - Fork 232
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
Add stored_data
and store_data
methods
#17
Comments
As mentioned in #16, JSON doesn't support common Python objects. That's the reason The lack of They should probably be added as a way to put data in the data directory, but I think they would also have to use Both the |
I've added a Pull Request with these features added. I didn't add an |
PS. This is all coming up because I'm rewriting ZotQuery from the ground up, and I'm really trying to take advantage of |
WRT permanent storage: data in the cache dir only gets deleted when a user explicitly deletes their caches using some tool like OnyX. It's generally a dumb idea to delete the cache unless something is going wrong: the data is there to speed things up. The difference is mostly semantic: data in caches is ephemeral or can be easily recreated; data stored in data directories is user-generated and can't be automatically recreated (e.g. settings). I'm certainly open to using the data directory as the storage for the |
BTW, what did you decide to do regarding search? Are you going to try |
Added |
I think I want to add
stored_data
andstore_data
to Workflow class. These methods would exactly mirrorcached_data
andcache_data
, but the data would be saved to the workflow's storage dir and nomax_age
would be required (i.e.max_age=0
is the permanent default).However, I was wondering if there was some larger reason that you didn't originally put these methods in that would keep you from accepting a later pull-request?
Also, I would prefer to serialize the data into JSON, as mentioned in Issue 16.
The text was updated successfully, but these errors were encountered: