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

Query Caching dependency tracking is not working for views and tables with __sql__ #97

Open
schirner opened this issue Mar 19, 2018 · 0 comments · May be fixed by #98
Open

Query Caching dependency tracking is not working for views and tables with __sql__ #97

schirner opened this issue Mar 19, 2018 · 0 comments · May be fixed by #98

Comments

@schirner
Copy link

schirner commented Mar 19, 2018

Enabling query caching as outlined in here works. The interface becomes much more responsive (especially with larger tables, and complex views).

However, the dependency tracking on when to invalidate the cached query does not work. The dependencies in the table's fields.ini, __dependencies__ are not observed. For tables that do have a __sql__, the dependency to itself is also not working. The cache is never invalidated, even when changing the table. The same limitation holds true for views. View caching works nicely (yay!), but dependency tracking with __source_tables__ and __dependencies__ defined in fields.ini does not work.

The cache invalidation seems only to work on simple tables (no __sql__ statement that grafts other fields).

I validated the table dataface__mtimes. Its entries get updated properly. The challenge seems to be with recording and checking the dependencies.

@schirner schirner linked a pull request Mar 19, 2018 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant