Query Results
When you run a query, Kvery shows the rows it returned in the results area below the editor. The same data can be viewed in three different ways, and you switch between them at any time without re-running the query.
The three result views
| View | Best for | Page |
|---|---|---|
| Table | Browsing, sorting and searching many rows | Tables |
| Cards | Reading one record at a time, key/value style | Cards |
| Chart | Spotting trends and comparing values visually | Charts |
The table is the default view. Cards and charts are rendered from the same result set, so you never lose data by switching — you are only changing how it is presented.
How rows are loaded
Results are paginated for speed: Kvery shows the first page of rows immediately and lets you page through the rest. By default a result table starts with 25 rows per page; on small dashboard tiles this drops to a few rows so the layout stays readable. Long text values are truncated in the cell (around 75 characters) with the full value available on demand, so a single wide column can't break the table.
Shaping the output with SQL
You control how each column behaves directly from your SQL using column modifiers — for example hiding a column, rendering it as JSON, disabling sort/search, or marking it as a long value. This means the result view is fully driven by the query itself; there are no hidden per-column settings to keep in sync.
What you can do next
- Export the result set or rely on Kvery's short-lived result cache — see Export and cache.
- Pin a result view onto a dashboard so it refreshes on demand.
- Publish the query as an API endpoint to get the same rows as JSON.