Schema Browser and Object Tree

The object tree is the main navigation surface in DBX. It displays more than databases, schemas, tables, and columns: it also manages connection groups, visible scope, object search, pins, copy/paste, schema actions, specialized workspaces, and administration views.

Connection and Object Hierarchy

A typical relational hierarchy looks like this:

Connection group
 └── Connection
      └── Catalog / database
           └── Schema
                └── Table / view / routine / other object
                     └── Column / index / foreign key / trigger

The actual hierarchy follows the database model:

Connection Groups and Bulk Management

• Create nested groups with custom subgroup names
• Drag connections into groups or use copy/paste and bulk movement
• Multi-select connections and use the toolbar for grouping, copying, disconnecting, and other batch actions
• Configure connection colors, notes, pins, read-only state, and production scope
• Copy a connection name or duplicate the full connection as a new entry
• Inspect host, port, database type, and other summaries in connection tooltips

Supported connection imports can retain group information. When sidebar layouts move between devices, DBX remaps connection IDs.

Expand, Collapse, and Pin

• Click a node to expand or collapse it
• Use Expand all or Collapse all for the current tree scope
• Pin frequent connections, databases, schemas, tables, or Nacos namespaces
• Keep the active database or important row visible while scrolling long lists
• Let open tabs select or reveal the related tree object

Pins improve navigation but do not mark production. Configure read-only and production state separately under Production and Write Safety.

Search and Filtering

Object-tree search can match:

• Connections, groups, databases, catalogs, and schemas
• Tables, views, columns, indexes, and selected database-specific objects
• Object paths, column comments, and table comments
• Loaded metadata and table lists that support server-side filtering

Some searches pass the keyword to the driver with debouncing, avoiding a full table load first. You can also restrict search by node type or use local table search inside the active database.

Visible-scope settings can hide databases, schemas, system schemas, or tables with configured prefixes. Newly created databases or schemas can be added to the visible list automatically.

Metadata Display

Depending on database and settings, the tree can show:

• Table and column comments
• Column type, nullability, default, and constraint summaries
• Object counts and loading state
• Table type plus catalog, schema, and database path
• MongoDB collection metadata
• Database-specific object types and status

Object metadata display is configurable. In large schemas, show only the extra information you need to reduce visual noise and metadata requests.

Open Data, Structure, and Source

Table, object, and data tabs use distinct identities so same-named objects do not incorrectly reuse a data tab.

Context Menus and Batch Actions

Context menus are generated from node type and database capabilities. Common actions include:

• Create, rename, or delete databases and schemas and edit supported comments, charsets, or collations
• Create, copy, paste, rename, truncate, or drop tables
• Copy/paste table structure or data across databases when the target driver supports it
• Open data, structure, DDL, source, ER diagram, field lineage, schema diff, and database search
• Import data, transfer data, execute SQL files, export databases, or back up supported file databases
• Generate SELECT, INSERT, UPDATE, DELETE, and other SQL templates
• Manage indexes, triggers, routines, extensions, users, jobs, and database-specific objects
• Open dashboards, processes/sessions, or specialized administration pages

Destructive actions are grouped more explicitly and appear or require confirmation based on read-only state, production scope, and database capability.

Copy, Paste, and Drag

• Copy connection, database, schema, table, column, or selected table names
• Choose database/schema qualification and identifier quoting where supported
• Drag tables or columns into the SQL editor to generate references
• Copy a table and paste into a compatible target to start structure or data transfer
• Reveal local file databases in the operating-system file manager

Cross-database copying involves type mapping, defaults, constraints, and identity semantics. Review Data Transfer and generated SQL first.

Database-Specific Hierarchies

DBX does not force every system into a relational tree. For example:

• SQL Server can expose linked servers and database objects
• Doris / StarRocks support external catalogs and three-part names for external tables
• MongoDB exposes collections, indexes, and GridFS
• Elasticsearch / Easysearch / Meilisearch model indexes as first-class objects
• Dameng, Oracle, PostgreSQL, and others can expose routines, jobs, extensions, or administration objects
• etcd, Nacos, message queues, and vector databases open dedicated workspaces from tree nodes

Safety and Performance Boundaries

• The tree shows only objects visible to the current account; missing objects often indicate database permissions
• Large schemas use lazy loading, caching, and server-side filtering; avoid expanding everything without a purpose
• System schemas, object counts, and extra metadata increase request volume and can be disabled
• Drop, truncate, cross-database paste, and administration actions may be irreversible; review backups and scope first
• Read-only connections hide or reject multiple mutation entry points, but database privileges remain the final boundary