Skip to content

Migrations

Migration Files

Migration documentation is stored as markdown files in each web app's migrations/ directory.

Admin Web App

Source: pharmanet-admin/migrations/

File Description
01_create_pharmacy_subscriptions.md Pharmacy subscription tracking
02_create_featured_product_payments.md Paid featured product placements
03_visibility_filters.md Subscription-based pharmacy visibility
04_create_promotions_and_offers.md Campaigns + seller discount offers

Seller Web App

Source: pharmanet-web/migrations/

File Description
01_create_pharmacy_subscriptions.md Pharmacy subscription tracking
02_create_featured_product_payments.md Paid featured product placements
03_visibility_filters.md Subscription-based pharmacy visibility

Master Migration SQL

A complete SQL migration file exists at the project root:

Source: /home/blackginger/Git-projects/pharmanet/supabase_complete_migration.sql

This file contains: - All table definitions (CREATE TABLE) - All indexes (CREATE INDEX) - All RLS policies (CREATE POLICY + ALTER TABLE ENABLE RLS) - Realtime publication setup (ALTER PUBLICATION) - Trigger functions and triggers - Enum type definitions (if used)

Applying Migrations

# Option 1: Supabase Studio SQL Editor
# Open SQL Editor → paste supabase_complete_migration.sql → Run

# Option 2: Prisma (web apps)
cd pharmanet-admin
npx prisma db push

# Option 3: psql directly
psql "$SUPABASE_DB_URL" -f supabase_complete_migration.sql

Migration Strategy

  • Prisma schema (prisma/schema.prisma) defines the desired state
  • npx prisma db push syncs the database to match the schema
  • Migration SQL files document manual changes (RLS, realtime, views, functions)
  • supabase_complete_migration.sql is the canonical full-database SQL for fresh setups
  • Schema — Table definitions