Sign In Download Free
Advanced

Schema & Objects

Inspecting structure — View Schema, object browsing, stats and schema-aware autocomplete.

View Schema (SQL Engines)

Right-click any table in the sidebar and choose View schema. Sutido opens a new tab with the schema query for that engine — columns, types, nullability and defaults from information_schema on PostgreSQL and SQL Server, and DESCRIBE TABLE on ClickHouse — and runs it for you. The result lands in the regular grid, so you can sort, copy or diff it like any other result.

How to: inspect a table's columns and types

  1. Expand the connection in the sidebar down to the table
  2. Right-click the table and choose View schema
  3. A new tab opens with the engine's schema query and runs it — the grid shows column names, types, nullability and defaults
  4. Sort or copy the result like any other — Ctrl+A, Ctrl+C gives you the whole schema as a pasteable table

The Object Browser

The sidebar shows each engine's real structure, not a generic tree:

  • PostgreSQL / SQL Server: tables, views, materialized views, functions, procedures, triggers and sequences, each in its own group
  • MongoDB: collections, system collections and views
  • Aerospike: namespaces and sets
  • ClickHouse: databases, tables and views (metadata comes from the system tables)

Hovering a table or collection shows a stats tooltip: row/document count, data size, storage size, index size and index count.

Schema-Aware Autocomplete

The same structural knowledge powers IntelliShell: table, collection and column names are suggested from your live connection, and for MongoDB, field names — including nested paths — are derived from your actual documents. Suggestions are cached for about five minutes, so a schema change shows up shortly after, or immediately after reconnecting.

Schema-Flexible Engines

MongoDB and Aerospike don't enforce a schema, so "the schema" is whatever your documents do. Two habits help:

  • Use the Tree view on a broad query to see the shapes that actually occur
  • Query for outliers explicitly, e.g. db.getCollection("customers").find({ email: { $exists: false } })

Next Steps

Indexes are part of the structure too — see Index Management.