aiox-data-engineer

To design a PostgreSQL schema with Row Level Security (RLS), model domain entities with baseline audit fields and foreign keys, then define a defense-in-depth RLS strategy with testing scenarios to prevent accidental data exposure in Supabase.

The best way to plan reversible database schema migrations is to snapshot, dry-run, apply, seed, rollback, and smoke-test changes. This ensures idempotent, versioned, and reversible database evolution with operational observability.

To optimize slow PostgreSQL queries for large datasets, analyze query behavior using explain-style analysis to improve indexing, joins, hot paths, and execution plans, ensuring performance-focused query modeling.

Yes, Supabase RLS supports defense-in-depth security controls. You can define and validate RLS strategies that include specific testing scenarios to prevent accidental data exposure and secure access control at the database architecture level.

You need rollback and snapshot strategies for PostgreSQL schema migrations to support reversible production evolution. They allow you to dry-run, apply, and smoke-test idempotent, versioned changes safely without risking database integrity.

A secure database schema architecture should include baseline auditing fields, constraints, and foreign keys for data integrity. It also requires versioned migrations and observability-oriented operational practices for reliable access control.