Export & Cache
Once a query has run, the result set is more than something to look at — you can take the data with you and reuse it programmatically.
Getting the data out
There are two complementary ways to get a result set out of Kvery:
- From the result view — copy or export the rows you are looking at for quick, one-off needs.
- As an API response — publish the query and call its endpoint to receive the same rows as JSON. This is the right approach for anything repeatable: spreadsheets, scripts, or another service.
Because the API returns exactly what the query returns, the
column modifiers you apply (such as ::json or
::hidden) shape the exported data too.
Result caching
Kvery keeps recent results around briefly so that re-opening a query or a dashboard tile feels instant instead of hitting the database again. This cache is short-lived and is meant for responsiveness, not as a data store — when you need fresh numbers, simply re-run the query.
For scheduled queries and dashboards, each run produces a fresh result, so the numbers you receive by email or see on a refreshed dashboard always reflect the latest execution.
Large result sets
The result view is paginated (25 rows per page by default) so the UI stays fast
no matter how many rows match. If you need every row in another system, call
the public API and page through the results there,
or narrow the query with WHERE / LIMIT so you only pull what you need.
Aggregate and filter in SQL before exporting. Pulling a pre-summarised result is far faster and cheaper than exporting raw rows and crunching them elsewhere.