mirror of
https://github.com/pezkuwichain/pwap.git
synced 2026-08-12 05:50:56 +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.
63 lines
1.7 KiB
PL/PgSQL
63 lines
1.7 KiB
PL/PgSQL
-- Payment proof lifecycle: auto-delete after 1 day, retain if disputed
|
|
|
|
-- 1. Add proof_expires_at column
|
|
ALTER TABLE public.p2p_fiat_trades
|
|
ADD COLUMN IF NOT EXISTS proof_expires_at TIMESTAMPTZ;
|
|
|
|
-- 2. Function to clean up expired payment proofs
|
|
-- Called by pg_cron or Edge Function daily
|
|
CREATE OR REPLACE FUNCTION cleanup_expired_payment_proofs()
|
|
RETURNS JSON AS $$
|
|
DECLARE
|
|
v_count INT := 0;
|
|
v_trade RECORD;
|
|
BEGIN
|
|
FOR v_trade IN
|
|
SELECT id, buyer_payment_proof_url
|
|
FROM p2p_fiat_trades
|
|
WHERE buyer_payment_proof_url IS NOT NULL
|
|
AND proof_expires_at IS NOT NULL
|
|
AND proof_expires_at < NOW()
|
|
AND status NOT IN ('disputed')
|
|
LOOP
|
|
UPDATE p2p_fiat_trades
|
|
SET buyer_payment_proof_url = NULL,
|
|
proof_expires_at = NULL,
|
|
updated_at = NOW()
|
|
WHERE id = v_trade.id;
|
|
|
|
v_count := v_count + 1;
|
|
END LOOP;
|
|
|
|
RETURN json_build_object('success', true, 'cleaned', v_count);
|
|
END;
|
|
$$ LANGUAGE plpgsql SECURITY DEFINER;
|
|
|
|
-- 3. Function to retain proof when dispute is opened (set expires_at = NULL)
|
|
CREATE OR REPLACE FUNCTION retain_payment_proof(p_trade_id UUID)
|
|
RETURNS JSON AS $$
|
|
BEGIN
|
|
UPDATE p2p_fiat_trades
|
|
SET proof_expires_at = NULL,
|
|
updated_at = NOW()
|
|
WHERE id = p_trade_id
|
|
AND buyer_payment_proof_url IS NOT NULL;
|
|
|
|
RETURN json_build_object('success', true);
|
|
END;
|
|
$$ LANGUAGE plpgsql SECURITY DEFINER;
|
|
|
|
-- 4. Moderator function to delete proof after dispute resolution
|
|
CREATE OR REPLACE FUNCTION moderator_clear_payment_proof(p_trade_id UUID)
|
|
RETURNS JSON AS $$
|
|
BEGIN
|
|
UPDATE p2p_fiat_trades
|
|
SET buyer_payment_proof_url = NULL,
|
|
proof_expires_at = NULL,
|
|
updated_at = NOW()
|
|
WHERE id = p_trade_id;
|
|
|
|
RETURN json_build_object('success', true);
|
|
END;
|
|
$$ LANGUAGE plpgsql SECURITY DEFINER;
|