Catalog

Triggers

Name: Nexoxa Bridge
Author: Nexoxa

BEFORE/AFTER triggers per table.

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.

Mystery updated_at changes, opens Triggers — BEFORE/AFTER per table — finds auto-touch trigger on invoices.

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

Bridge path: /database/triggers

Step 1

Audit trigger definitions

BEFORE UPDATE sets updated_at — documented for junior devs.
No folklore triggers.

BEFORE/AFTER triggers per table. /database/triggers. Per-table trigger list.

Step 2

Before migrations

Drop trigger temporarily during bulk load — catalog shows exact name for migration script.
Copy-paste safe.

Names and timing (BEFORE/AFTER) for scripts.

Step 3

Link to functions

Trigger function body inspected via Functions panel.
Full chain visible.

Navigate to Functions from trigger metadata.

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