db-write

Safely run mutating SQL on Supabase by using guardrails that require explicit user confirmation before executing mutations in non-local environments. This enforces environment checks and targets specific databases to prevent accidental data changes.

Executing database migrations and data fixes on dev environments is best handled by targeting the dev environment explicitly and previewing changes. The system defaults to local but supports dev and preview environments with required confirmation before execution.

You can preview schema changes and seed data before applying them to a Supabase database. The system provides safe defaults with options to preview changes, ensuring safe migrations and schema updates before committing to execution.

Running SQL mutations on Supabase requires explicit user confirmation for remote execution. Guardrails enforce this confirmation in non-local environments, including dev, preview, and production, to ensure all changes are deliberate and auditable.

You need guardrails for Supabase SQL mutations and schema updates because mutating SQL can lead to accidental data changes or downtime. Guardrails provide explicit invocation and environment checks to ensure changes are deliberate and auditable.