Docs/Data Explorer

Examining Table Structure

The structure view provides the metadata you need before editing data, writing SQL, or configuring a stream.

Columns tab

The Columns tab shows the detailed shape of the selected object.

Typical fields include:

  • name
  • data type
  • length or enum values where applicable
  • default value
  • nullability
  • auto-increment behavior
  • comments when available

Keys tab

The Keys tab surfaces relationship-critical metadata.

This includes:

  • primary keys
  • foreign keys
  • unique constraints
  • referenced tables and actions where the engine exposes them

Indexes tab

The Indexes tab helps explain access patterns and tuning assumptions.

You can review:

  • index name
  • index type
  • uniqueness
  • indexed columns and sort direction
  • additional metadata returned by the engine

Triggers tab

The Triggers tab lists triggers defined on the selected table.

Each trigger shows:

  • trigger name
  • timing (BEFORE / AFTER) and event (INSERT / UPDATE / DELETE)
  • trigger body with syntax highlighting

DDL tab

The DDL tab shows the SQL definition retrieved for the selected object.

Use it to:

  • validate the exact source definition before migration work
  • capture schema details for tickets or reviews
  • compare source and target structure expectations
  • copy the definition into external tooling when needed

File and S3 structure

When viewing a file-backed table (local files or S3), the Structure tab adapts to show file-specific metadata instead of database-specific tabs.

File info

The top of the Structure view shows:

  • Format badge — file format (e.g., PARQUET, CSV, JSON)
  • Row and column counts — total rows and number of columns
  • File size — size on disk
  • File path — full path with Copy and Reveal in Folder buttons (local files only)

Columns

File structure shows a simplified column list:

FieldDescription
ColumnColumn name
TypeInferred data type
NullableWhether the column allows null values

Keys, Indexes, and DDL tabs are not shown for file-backed tables.