Table Categories

The DB tree separates objects such as tables, views, routines, and sequences by type. In ERD workflows, you find tables from these categories, add them to the current ERD, or refresh them.

DB Tree Categories

TABLES and VIEWS are separated by default, and categories such as INDEXES, SEQUENCES, ROUTINES, TRIGGERS, and EVENTS are added depending on the DBMS.

Category	Relation to ERD
TABLES	A list of regular tables that can be added to an ERD.
VIEWS	Read-only/query objects. Some editing can be restricted compared with regular tables.
ROUTINES	Groups FUNCTIONS and PROCEDURES together in DBMSs such as PostgreSQL and Oracle.
Other objects	Used more often from object detail tabs or SQL generation than as direct ERD table nodes.

Add from Category to ERD

Tables in the TABLES category can be dragged onto the canvas or added to the current ERD from the context menu. A specific-Schema ERD allows only tables from the same Schema, while an all-Schema ERD can also include tables from other Schemas in the same Connection and Database.

Note:

Tables marked as system Schema appear in grayscale/locked state, and structural changes are restricted.

When an ERD tab is active, the related Connection, Database, and Schema are highlighted in the left DB tree, and the tree automatically scrolls to make that location visible.

Refresh Categories

Refresh on a category node reloads that category list. Refresh when tables were changed externally or when the list looks stale after applying DB changes from the ERD.

Situation	Recommended Action
Table created externally	Refresh the Schema or TABLES category.
List update after DDL Import	If needed, refresh the TABLES category and confirm the imported table.
Check structure after applying to DB	Refresh the table or category to inspect the latest structure.

DBMS Differences

Category composition differs by DBMS. For example, PostgreSQL and Oracle functions/procedures can be grouped as ROUTINES in the tree, and some DBMSs may not show certain categories.