Result views
Six ways to read a result set: table, tree, JSON, result, explain, and chart.
Checked against v1.11.0 Updated
- Six view modes: Tree, Table, JSON (the result as formatted text), Result (a write outcome or single value as a card of copyable metrics), Explain, and Chart (Pro)
- Active mode persists per tab. Set Tree or Table as the default for new queries, or restore automatic selection
- Fullscreen: Tab (results fill the tab) or Window (results fill the app), exit with Escape
- Collapsible result panel and a resizable editor/result split, both persisted per tab
- Preview drawer (Ctrl/Cmd+I) follows row focus in Tree and Table, showing the document as formatted JSON
- Tree view: keyboard expand and collapse, MongoDB-aware type badges, resizable columns, and sticky document headers, up to five nesting levels at once, which can be switched off for the whole app
- Table view: column sorting, resize, auto-fit, pinning, and reorder, persisted per tab and in favorites
- Headers identify the predominant column type
- Ctrl/Cmd+F searches the loaded result set, highlighting individual matches in keys, cells, and nested values
- Crossing a page boundary moves to the next loaded match. It does not issue a server-side search or fetch past the result cap
- Hover an Object or Array cell for a moment and a read-only preview opens, closing on scroll or when the row is expanded
- Expand complex values inline with a nested tree, breadcrumb path, editable leaves, and a resizable panel
- Result cap with cursor pagination. Load 5K / 10K / All when capped, offering only the choices above the current cap
- Loading everything warns first that a large collection may be slow
- Auto-explain badge on every read that returns a cursor: green IXSCAN with index name, or red COLLSCAN, with the full plan on hover
- Collection is skipped for multi-statement code, for a value that is not a cursor, for a query that explains itself, for a pipeline carrying $out or $merge, and when the connection’s auto-explain setting is off. The statistics come from running the query a second time, which is why a possible write is never explained
- Empty result sets still show timing and explain information
- Pagination with previous, next, and direct page entry. Page sizes of 10, 25, 50, 100, 200, 500 and 1,000, or any value from 1 to 1,000. A larger number is clamped to 1,000