supabase-migration

You generate and validate Supabase migrations that specifically enforce period locks, immutability, and auditability. This ensures your database schema satisfies Swedish legal-compliance requirements for accounting data.

Using a table template blueprint ensures correct RLS policies and triggers when adding new Supabase tables. It automatically includes a UUID primary key, user_id foreign key, timestamps, and necessary constraints.

You set up a 7-year retention rule by implementing compliance guidance within your Supabase migration scripts. This enforces BFL retention requirements directly in the database schema, ensuring records are preserved correctly.

Supabase migration numbering uses deterministic, sequential IDs for each generated migration file. This ensures consistent ordering and reliable tracking of schema changes across different deployment scenarios.

Yes, you can validate triggers and audit-trail requirements before deployment. The migration generator validates Supabase scripts to ensure row-level security policies and audit-trail requirements are properly implemented.

When modifying constraints across deployment scenarios, Supabase migrations must maintain immutability and period locks. Changes are strictly constrained by the need to satisfy legal-compliance requirements and preserve 7-year retention rules.