Catalog

Enums & custom types

Name: Nexoxa Bridge
Author: Nexoxa

Enum labels, composite types, and domains.

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.

ORM enum mismatch breaks deploy, opens Enums — labels, composite types, domains — aligns TypeScript union with Postgres labels.

The Catalog panel Enums 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 Enums from the left sidebar after you connect; everything here reflects the live connection, not a cached export from yesterday.

Bridge path: /database/types

Step 1

Enum labels

status enum missing pending_payment — add label migration written from catalog list.
ORM syncs.

Enum labels, composite types, and domains. /database/types. Enum labels and custom types.

Step 2

Composite and domains

address composite type fields listed — API serializer fixed.
Domains with constraints visible.

Composite types and domains introspection.

Step 3

Generate ALTER TYPE

Copy label list into migration PR description.
Reviewers see source of truth.

Pair with Query lab for ALTER TYPE ... ADD VALUE.

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