Catalog

Schema map & ER diagram

Name: Nexoxa Bridge
Author: Nexoxa

Tables, foreign keys, and an interactive ER diagram.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Writing a JOIN across five tables, opens Schema map because the ER diagram shows the shortest path from orders to products — FK lines clearer than a wall of SQL.

The Catalog panel Schema map is where Bridge turns raw metadata into decisions — counts, definitions, dependencies, and links into the grid or Query lab. No information_schema archaeology; no guessing which mat view is stale.

Open Schema map from the left sidebar after you connect; everything here reflects the live connection, not a cached export from yesterday.

Bridge path: /database/schemas

Step 1

Interactive ER diagram

Drag zooms; click table highlights FK edges. The path from orders → line_items → products is obvious.
Screenshot goes into design doc.

Tables, foreign keys, and an interactive ER diagram. /database/schemas. Tables and FK relationships from live metadata.

Step 2

Before you migrate

Dropping a column — diagram shows three inbound FKs. Migration order writes itself.
Fewer Friday afternoon surprises.

Pair with Foreign keys and Knowledge graph for community-level view.

Step 3

Shared mental model

Team standup references the same diagram Copilot uses — words align with picture.
Less arguing about whether clients connects to invoices.

Graph feeds db-knowledge-out reports for AI context.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

Database connection URLs