aiox-data-engineer

Designing a secure Supabase schema involves translating domain requirements into normalized tables with audit fields, then applying defense-in-depth RLS policies validated through positive and negative access-control test cases to enforce data security.

The safest way to execute PostgreSQL schema migrations is using snapshot-first operations that are idempotent and reversible, ensuring you can rollback changes safely while preventing production data corruption during schema refactors.

To optimize slow PostgreSQL queries, you analyze hot paths and query execution plans, then implement indexing strategies and query refactoring to eliminate inefficient joins and reduce full table scans for real workloads.

RLS policies may allow unauthorized access if they lack defense-in-depth validation, which requires testing access rules against both positive and negative realistic user contexts to verify proper access-control enforcement across all tables.

Yes, domain-to-schema modeling translates business requirements directly into normalized schemas with consistent audit fields, constraints, and relationships, generating the necessary database architecture without starting from manual SQL scripts.

Without observability-oriented outcomes across design-to-deploy workflows, you cannot effectively monitor schema refactors, migration execution safety, or RLS validation, limiting your ability to detect and prevent performance degradation or access control failures.