Catalog

Database knowledge graph

Name: Nexoxa Bridge
Author: Nexoxa

FK communities and god nodes — built on connect.

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.

Friday migration on wide schema, opens Knowledge graph — FK communities and god nodes in graph.html — screenshots change request.

The Catalog panel Knowledge graph 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 Knowledge graph 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 graph.html

clients hub connects half the schema — migrate clients last. Interactive zoom proves it to PM.
Built on connect locally.

FK communities and god nodes — built on connect. /database/schemas. graph.html from metadata. Pro feature.

Step 2

God nodes and communities

God node report in db-knowledge-out — Cursor rules reference same graph.
AI and humans share map.

Reports in db-knowledge-out/. No credential upload.

Step 3

Copilot reads the graph

Ask migration order — answer cites communities from graph.
Fewer risky Fridays.

Pair with Copilot and FOREIGN KEYS panel.

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