mirror of
https://github.com/pezkuwichain/pwap.git
synced 2026-08-12 12:31:34 +00:00
pezkuwichain
e18ba679be
The migrations did not describe this database, and could not be made to.
Three findings, in the order they surfaced:
* 25 functions declared across six migrations — all recorded as applied — did
not exist. Their tables did. Two were reached by the app, so merchant tier
upgrades and post-trade reputation updates had been quietly dead. This only
came to light because a user hit "Could not find the function
public.upsert_user_profile(...)" while toggling a notification setting.
* admin_roles has three conflicting definitions across the set and production
matches none of them. 001 says (id, user_id, role, granted_by, granted_at),
COMBINED says (user_id, role, created_at), production has
(id, user_id, role, permissions, created_at, updated_at).
* Applied to an empty database, five migrations fail. The legacy 0NN filenames
sort before the 14-digit timestamps they depend on — "013" < "20241117054600"
— so 013 runs before the migration creating the table it alters. The set
could never have been replayed from scratch.
So it could not be tested, could not rebuild the database, and did not match what
was running. Widening or patching it would have been dressing up a history that
was already fiction.
The baseline is a pg_dump of the live public schema, which matches production by
construction. Privileges are included deliberately: the REVOKEs on
lock_escrow_internal, release_escrow_internal, refund_escrow_internal and
request_withdraw are the 20260725030000 hardening, and dropping them would hand
fund movement back to anon.
Verified step by step against production before committing:
- applies to an empty database cleanly, after three real obstacles were fixed
(extensions live in the `extensions` schema, supabase_admin membership,
platform-level ALTER DEFAULT PRIVILEGES that cannot apply outside Supabase)
- produces 83 tables / 39 functions / 222 indexes / 360 policies — identical
counts to production
- recorded as applied in supabase_migrations without touching the 37 existing
rows, then dry-run confirmed "up to date — no pending migrations", so the
next deploy will not try to replay it over live tables
- drift check now reports "every declared function is present"; the known-gaps
list drops from 22 entries to zero
The old files move to migrations/archive/ rather than being deleted — they are
the only record of why parts of this look the way they do. Their README says
plainly not to run them, and why.
CI now applies migrations to an empty Postgres on every PR. That check was
impossible while the old set was the starting point; it is the thing that stops
this class of drift from being discovered by a user again.
80 lines
2.4 KiB
SQL
80 lines
2.4 KiB
SQL
-- ========================================
|
|
-- Add Missing Columns to Profiles Table
|
|
-- ========================================
|
|
-- Run this in Supabase SQL Editor
|
|
-- Dashboard → SQL Editor → New Query → Paste & Run
|
|
|
|
-- Add bio column
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS bio TEXT;
|
|
|
|
-- Add phone column
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS phone TEXT;
|
|
|
|
-- Add language column (default: 'en')
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS language TEXT DEFAULT 'en';
|
|
|
|
-- Add theme column (default: 'dark')
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS theme TEXT DEFAULT 'dark';
|
|
|
|
-- Add notification preferences
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS notifications_email BOOLEAN DEFAULT true;
|
|
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS notifications_push BOOLEAN DEFAULT false;
|
|
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS notifications_sms BOOLEAN DEFAULT false;
|
|
|
|
-- Add 2FA column
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS two_factor_enabled BOOLEAN DEFAULT false;
|
|
|
|
-- Add location and website columns (for completeness)
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS location TEXT;
|
|
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS website TEXT;
|
|
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS phone_number TEXT;
|
|
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS recovery_email TEXT;
|
|
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS recovery_email_verified BOOLEAN DEFAULT false;
|
|
|
|
-- Add email_verified (for compatibility, though we prefer user.email_confirmed_at)
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS email_verified BOOLEAN DEFAULT false;
|
|
|
|
-- Add joined_at column
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS joined_at TIMESTAMP WITH TIME ZONE DEFAULT TIMEZONE('utc'::text, NOW());
|
|
|
|
-- Add role column
|
|
ALTER TABLE public.profiles
|
|
ADD COLUMN IF NOT EXISTS role TEXT DEFAULT 'Member';
|
|
|
|
-- Create indexes for frequently queried columns
|
|
CREATE INDEX IF NOT EXISTS idx_profiles_phone ON public.profiles(phone);
|
|
CREATE INDEX IF NOT EXISTS idx_profiles_language ON public.profiles(language);
|
|
CREATE INDEX IF NOT EXISTS idx_profiles_location ON public.profiles(location);
|
|
|
|
-- Update existing users' joined_at to their created_at if null
|
|
UPDATE public.profiles
|
|
SET joined_at = created_at
|
|
WHERE joined_at IS NULL;
|
|
|
|
-- Success message
|
|
DO $$
|
|
BEGIN
|
|
RAISE NOTICE 'Profile columns added successfully!';
|
|
END $$;
|