Results & Documents

Three Views of Every Result

Switch views with the selector in the results toolbar:

• Table — a fast virtualized grid with typed cells (int32, float64, boolean, datetime, object, array, null shown with type chips), resizable columns, and drill-down into nested data with breadcrumbs leading back
• JSON — raw documents with syntax highlighting, ideal for copying
• Tree — expandable nodes for exploring deeply nested documents

The Grid Is a Spreadsheet

Select rows (Click, Shift+Click, Ctrl+Click, Ctrl+A for all) and columns (click headers, Ctrl+Click for more), then copy exactly the shape you need — see Clipboard & Export. The sort arrows in each column header order any column ascending, descending, or back to query order — stable and type-aware, with nulls last.

Right-clicking a cell opens more power tools:

• Filter by this value — opens a filtered query in a new tab
• Open row as query — jump to the exact document
• Compare selected rows — a field-by-field diff of two rows
• Copy as SQL IN list or Markdown table

Paging & Counts

First/previous/next/last paging with a configurable page size (default 50, up to 10 000). The full document count runs in the background with its own abort, so a slow count() never blocks you.

Viewing & Editing Documents

• F3 — read-only document inspector
• Ctrl+J — edit: Sutido generates the update script and shows it to you before it runs
• Add document — insert via a modal
• Delete — previews the delete script and shows how many documents are affected before you confirm

Delete Recovery

MongoDB deletes are journaled locally before they run (up to 1000 documents per operation), and so are edits you make in the grid. Aerospike deletes are journaled too: AQL deletes by primary key, so the record is read and stored before it goes.

How to: restore documents you just deleted

1. Open the Changelog panel
2. Find the delete operation — entries show the collection or set, the operation type and the affected records, with the pre-delete state preserved
3. Select the entry and click Revert
4. Confirm — deleted records are written back; for edits, the previous state replaces the current one

Two things worth knowing. An Aerospike record comes back with its bins exactly as they were, including map and list bins — the restore goes through the driver rather than generated AQL, which has no literal form for either — but it starts again on the namespace default time-to-live rather than the remainder it had. And where nothing can be journaled at all — drop(), TRUNCATE, any SQL DELETE — Sutido shows you what is about to be destroyed instead of promising a recovery it cannot deliver.

How to: compare two rows field by field

1. Click the first row, then Ctrl+Click the second
2. Right-click either row and choose Compare selected rows
3. The diff modal highlights every field that differs — Escape closes it

MongoDB Types

BSON has types JSON does not, and the right spelling depends on what you are about to do with the text. Pick one in the results toolbar, or under Settings → Appearance → BSON display format:

• Shell (default) — ObjectId("…"), ISODate("…"), NumberLong("42"). Not valid JSON, but the only format you can paste straight back into a query.
• Extended JSON — {"$oid": "…"}. Valid JSON and lossless; what mongoexport and the drivers speak.
• Plain JSON — "…", 42. Reads well anywhere else, and loses the type: it cannot be turned back into BSON.

The choice covers the grid, the JSON and tree views, the shell output and everything you copy. It never reaches anything that writes back: restoring from the changelog and editing a document always use a lossless format, whatever is selected. Regular expressions show as /pattern/flags, and a 64-bit long is never emitted as a JSON number — rounding an identifier silently is worse than a wide cell. SQL results show their column types as chips in the header and cells.

Next Steps

Master the clipboard formats — the fastest way to get data out of Sutido and into Excel, scripts, or tickets.