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 / triggerThe actual hierarchy follows the database model:
| Type | Example tree |
|---|---|
| MySQL-compatible | Connection → database → table/view → column/index/foreign key/trigger |
| PostgreSQL, Oracle, SQL Server, and others | Connection → database or service → schema → object |
| Doris / StarRocks | Catalog → database → table when multiple catalogs exist; flat when only internal exists |
| Redis | Connection → Redis DB, with paged keys in the dedicated browser |
| MongoDB | Connection → database → collections, indexes, and GridFS buckets |
| Elasticsearch / Easysearch / Meilisearch | Connection → indexes and other document objects |
| Apache CouchDB | Connection → CouchDB databases as document collections |
| HBase, vector, message queue, etcd, ZooKeeper, Nacos | System-specific objects that open Specialized Workspaces |
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 complete cached table/view indexes
The main sidebar search reuses table/view indexes from memory or the persisted schema cache. When an index is missing, the first search builds it for the eligible scopes in the active, connected datasource. Further edits filter the index locally without reloading the datasource tree. With “Search only opened databases” enabled, search does not load objects from unopened databases, even when none are open. Connection and database names remain searchable, and you can expand a database to load its objects. Turn the setting off to search every visible database in the active connection.
Other supported object types (including procedures, functions, triggers, sequences, and packages) use debounced, on-demand remote search, even when their group has never been expanded or the object is beyond its first page. Matching pages are cached in memory by keyword and full scope; filtered results are not treated as a complete schema index. Changing the input cancels the previous remote request and discards late results. Search results do not replace the loaded browsing tree.
Enable Local search to search loaded objects and existing cached indexes without building missing indexes or making remote requests. Regex search also uses existing indexes only. You can restrict results by node type or use the separate table search inside a database.
Use Refresh to update cached metadata after external schema changes. Database and schema refreshes, including refreshes triggered by DBX object changes, invalidate the affected indexes.
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
While editing a procedure or function, use the eye icon beside Save to preview the update SQL. Both the object-browser source panel and the separate source dialog show all statements produced from the current draft by the database's existing save builder, including MySQL DROP and CREATE statements. The preview can be copied but never saves the draft or executes a database write. Editing the draft or switching objects or connections invalidates it. Saving retains the existing read-only, production-confirmation, and object-version checks.
| Action | Result |
|---|---|
| Open table | Opens the Data Grid |
| View structure | Opens columns, indexes, foreign keys, triggers, and DDL tabs |
| Edit table structure | Opens the Table Structure Editor |
| View DDL | Reads database- or driver-generated object definition |
| Open source | Shows view, procedure, function, trigger, or other source in a side panel or editor |
| Locate query object | Finds the table at the editor cursor or drags table/column references into SQL |
| Open specialized object | Opens Redis, MongoDB, vector, HBase, MQ, etcd, ZooKeeper, or Nacos workspaces |
Table, object, and data tabs use distinct identities so same-named objects do not incorrectly reuse a data tab.
Open Triggers from a Schema or Owning Object
For Oracle, OceanBase Oracle, and DM8, drivers that provide exact trigger metadata expose a schema-level Triggers group as well as triggers under their actual owning table or view. Same-named triggers with different owners remain separate objects. Trigger owner, owning-object owner, and execution schema are shown separately rather than inferred from tree labels.
- Open source from the trigger menu using the configured dialog or source-tab mode.
- Create from a schema, an empty trigger group, or an owning table/view menu. Choose the name and a supported scope, then generate, edit, and preview the complete definition. Non-table triggers show their actual scope without an invented parent table.
- Menus expose enable, disable, compile, and drop according to the driver's capabilities. Tree batch deletion retains same-type selection: review all SQL before serial execution. An unverified step stops the remaining steps.
An unknown result keeps the original row. Use Verify without writing in the error details to inspect the database before attempting another deletion. See Object Browser for state meanings and source recovery.
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
- Apache CouchDB lists each database as a document collection
- 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
Browse all objects
Use list or grid views for tables, views, routines, and statistics.
Edit table structure
Change columns and indexes and review DDL before execution.
Search the database
Locate objects by type, name, and metadata in large databases.
Manage specialized systems
Open Redis, MongoDB, vector, MQ, etcd, ZooKeeper, and Nacos workspaces.