Arnas Donauskas aee1621e44 fix: make migration idempotent ... The Supabase GitHub integration re-runs migrations on every push. The original 001_initial_schema.sql used plain CREATE TABLE without IF NOT EXISTS, so it failed with "relation 'profiles' already exists" after the first successful run. Changes: - CREATE TABLE -> CREATE TABLE IF NOT EXISTS (all 16 tables) - CREATE INDEX -> CREATE INDEX IF NOT EXISTS - DROP POLICY IF EXISTS before each CREATE POLICY (Postgres has no CREATE POLICY IF NOT EXISTS) - DROP TRIGGER IF EXISTS before each CREATE TRIGGER - Wrapped ALTER PUBLICATION in DO block that checks pg_publication_tables - handle_new_user() trigger now uses SECURITY DEFINER, SET search_path, EXCEPTION handler, and owner=postgres to properly bypass RLS on the profiles INSERT during signup (fixes "Database error saving new user") The migration is now safe to re-run any number of times. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-16 19:46:41 +03:00
..
migrations	fix: make migration idempotent	2026-04-16 19:46:41 +03:00