supabase-sql-inserter

name	supabase-sql-inserter
description	Insert missing or mismatched data into Supabase/Postgres tables using SQL. Use when asked to compare source data against existing tables, identify missing employees, and generate INSERT statements for the employees table or related tables.

Supabase SQL Inserter

Follow this workflow to compare source data against existing tables and generate safe SQL inserts for missing employees.

Scope

• Use SQL only (Supabase SQL editor or psql).
• Focus on employees inserts unless the user explicitly requests other tables.
• Generate SQL and validation queries; do not execute writes unless explicitly asked.

Workflow

1. Identify the source of truth for incoming data (CSV, staging table, query output, or manual list).
2. Choose match keys for comparison (prefer a stable business key; ask if unclear).
3. Stage the source data in SQL (CTE or temp table).
4. Compare staged data to employees and categorize:
   • Missing rows (in source, not in employees)
   • Mismatched fields (in both, differing values)
5. Generate INSERTs for missing rows and provide a verification query.

Match key guidance

• Prefer a unique business key. Common options: numero_empleado + cliente_id + empresa_id.
• If numero_empleado is not reliable, use rfc or curp (confirm with user).
• Always include cliente_id and empresa_id when available to avoid cross-tenant collisions.

Output expectations

Provide:

• A clear summary of missing rows found.
• The SQL INSERT for missing employees (or a CTE-based insert).
• A verification query that returns the inserted rows.

References

• Use references/employees.md for the current employees table columns and defaults.
• Use shared/schema.ts as the primary schema source when columns are unclear.