You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To simplify off-line work, I propose a feature for caching fetch results to enable repeated execution of the code without accessing the database. It would look something like
withdj.caching(refresh=True): # change to False after first executionformintuning.Maps&'animal_id = 17797':
plot_ori_map(m['ori_map'])
Caching cannot overlap with transactions and thus cannot be used inside make methods. Caching is ideal for exploratory and debugging purposes, not for pipeline work when data integrity is paramount. For example, working on figures or developing a new algorithm would be good use scenarios for that.
The caching filepath would be set in dj.config['query_cache'].
I need this feature for my own paper.
The text was updated successfully, but these errors were encountered:
To simplify off-line work, I propose a feature for caching fetch results to enable repeated execution of the code without accessing the database. It would look something like
or
Caching cannot overlap with transactions and thus cannot be used inside
make
methods. Caching is ideal for exploratory and debugging purposes, not for pipeline work when data integrity is paramount. For example, working on figures or developing a new algorithm would be good use scenarios for that.The caching filepath would be set in
dj.config['query_cache']
.I need this feature for my own paper.
The text was updated successfully, but these errors were encountered: