We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have a FAQ entry "My cached SQLite ontology is out of date" https://incatools.github.io/ontology-access-kit/faq/troubleshooting.html#my-cached-sqlite-ontology-is-out-of-date
This recommends low-level navigating to the pystow .data directly and explicitly clearing old .db files.
.data
However, since 0.6.17 we have had much better cache management tools captured in the release notes here:
https://github.com/INCATools/ontology-access-kit/releases/tag/v0.6.17
We have two commands:
And also a global option:
--caching CACHE-POLICY Set the cache management policy
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We have a FAQ entry "My cached SQLite ontology is out of date"
https://incatools.github.io/ontology-access-kit/faq/troubleshooting.html#my-cached-sqlite-ontology-is-out-of-date
This recommends low-level navigating to the pystow
.data
directly and explicitly clearing old .db files.However, since 0.6.17 we have had much better cache management tools captured in the release notes here:
https://github.com/INCATools/ontology-access-kit/releases/tag/v0.6.17
We have two commands:
And also a global option:
--caching CACHE-POLICY Set the cache management policy
The text was updated successfully, but these errors were encountered: