mirror of
https://github.com/pezkuwichain/pwap.git
synced 2026-10-20 18:56:16 +00:00
Satoshi Qazi Muhammed
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.
86 lines
2.6 KiB
SQL
86 lines
2.6 KiB
SQL
-- Perwerde (Education) Tables
|
|
-- Courses Table (ID comes from blockchain)
|
|
CREATE TABLE IF NOT EXISTS public.courses (
|
|
id BIGINT PRIMARY KEY, -- Blockchain course_id
|
|
owner TEXT NOT NULL,
|
|
name TEXT NOT NULL,
|
|
description TEXT,
|
|
content_link TEXT, -- IPFS hash
|
|
status TEXT NOT NULL DEFAULT 'Active',
|
|
created_at TIMESTAMP WITH TIME ZONE NOT NULL
|
|
);
|
|
|
|
-- Enrollments Table
|
|
CREATE TABLE IF NOT EXISTS public.enrollments (
|
|
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
|
|
student_address TEXT NOT NULL,
|
|
course_id BIGINT REFERENCES public.courses(id) ON DELETE CASCADE,
|
|
enrolled_at TIMESTAMP WITH TIME ZONE NOT NULL,
|
|
completed_at TIMESTAMP WITH TIME ZONE,
|
|
points_earned INTEGER DEFAULT 0,
|
|
is_completed BOOLEAN DEFAULT false,
|
|
UNIQUE(student_address, course_id)
|
|
);
|
|
|
|
-- Indexes
|
|
CREATE INDEX IF NOT EXISTS idx_courses_status ON public.courses(status);
|
|
CREATE INDEX IF NOT EXISTS idx_enrollments_student ON public.enrollments(student_address);
|
|
CREATE INDEX IF NOT EXISTS idx_enrollments_course ON public.enrollments(course_id);
|
|
|
|
-- RLS Policies
|
|
-- Courses
|
|
ALTER TABLE public.courses ENABLE ROW LEVEL SECURITY;
|
|
|
|
DROP POLICY IF EXISTS "Anyone can view courses" ON public.courses;
|
|
CREATE POLICY "Anyone can view courses"
|
|
ON public.courses FOR SELECT
|
|
USING (true);
|
|
|
|
DROP POLICY IF EXISTS "Admins can manage courses" ON public.courses;
|
|
CREATE POLICY "Admins can manage courses"
|
|
ON public.courses FOR ALL
|
|
USING (
|
|
EXISTS (
|
|
SELECT 1 FROM public.admin_roles
|
|
WHERE user_id = auth.uid()
|
|
)
|
|
);
|
|
|
|
-- Enrollments
|
|
ALTER TABLE public.enrollments ENABLE ROW LEVEL SECURITY;
|
|
|
|
DROP POLICY IF EXISTS "Users can view their own enrollments" ON public.enrollments;
|
|
CREATE POLICY "Users can view their own enrollments"
|
|
ON public.enrollments FOR SELECT
|
|
USING (
|
|
EXISTS (
|
|
SELECT 1 FROM public.wallets
|
|
WHERE user_id = auth.uid() AND address = student_address
|
|
)
|
|
);
|
|
|
|
DROP POLICY IF EXISTS "Users can create their own enrollments" ON public.enrollments;
|
|
CREATE POLICY "Users can create their own enrollments"
|
|
ON public.enrollments FOR INSERT
|
|
WITH CHECK (
|
|
EXISTS (
|
|
SELECT 1 FROM public.wallets
|
|
WHERE user_id = auth.uid() AND address = student_address
|
|
)
|
|
);
|
|
|
|
DROP POLICY IF EXISTS "Admins or course owners can update enrollments" ON public.enrollments;
|
|
CREATE POLICY "Admins or course owners can update enrollments"
|
|
ON public.enrollments FOR UPDATE
|
|
USING (
|
|
EXISTS (
|
|
SELECT 1 FROM public.admin_roles
|
|
WHERE user_id = auth.uid()
|
|
) OR
|
|
EXISTS (
|
|
SELECT 1 FROM public.courses c
|
|
JOIN public.wallets w ON c.owner = w.address
|
|
WHERE c.id = course_id AND w.user_id = auth.uid()
|
|
)
|
|
);
|