Cache parsed queries #91

Open
opened 2020-08-06 16:54:45 +00:00 by gburd · 0 comments
gburd commented 2020-08-06 16:54:45 +00:00 (Migrated from github.com)

For a given open database, and a given schema, we only need to process a query once — we can get all the way through to SQL and projections, and re-run multiple times.

Note that this is only true if the bindings in the query don't affect the analysis. I believe we're currently safe in this regard.

We can invalidate the cache when the schema changes.

Caching should be opt-in via an optional argument to <q.

For a given open database, and a given schema, we only need to process a query once — we can get all the way through to SQL and projections, and re-run multiple times. Note that this is only true if the bindings in the query don't affect the analysis. I believe we're currently safe in this regard. We can invalidate the cache when the schema changes. Caching should be opt-in via an optional argument to `<q`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/mentat#91
No description provided.