Skip to content
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

Cache internal results #24

Open
alecandido opened this issue Mar 1, 2022 · 0 comments
Open

Cache internal results #24

alecandido opened this issue Mar 1, 2022 · 0 comments
Labels
database Data persistence model enhancement New feature or request

Comments

@alecandido
Copy link
Member

This is something we're already doing in ekomark (it's part of the sandbox mode), and we can lift here.

In any case, it has a completely different role than external, and it should have even a different life-cycle: if we change the code and rerun, the internal cache should not be used, but nothing would have changed the external one.

So, we can do this with an extra table (e.g. InternalCache), and explicitly opt-in (even though I'd like to avoid interactive prompts, they are annoying in a lot of ways...).

@alecandido alecandido added database Data persistence model enhancement New feature or request labels Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database Data persistence model enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant