pacnpal/thrilltrack-explorer
1
0
Fork 0
mirror of https://github.com/pacnpal/thrilltrack-explorer.git synced 2025-12-27 02:46:58 -05:00
Code Issues Packages Projects Releases Wiki Activity

Reverted to commit 026a4e9362

Browse Source
This commit is contained in:
gpt-engineer-app[bot]
2025-09-30 20:10:02 +00:00
parent 6f1544309e
commit 9319aadfed
8 changed files with 13 additions and 706 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
supabase/migrations/20250930183419_97666361-7c5e-4875-863a-424c6018ffbc.sql
View File

@@ -1,21 +0,0 @@
-- Add escalation tracking fields to content_submissions table
ALTER TABLE public.content_submissions
ADD COLUMN IF NOT EXISTS escalated BOOLEAN DEFAULT FALSE,
ADD COLUMN IF NOT EXISTS escalation_reason TEXT,
ADD COLUMN IF NOT EXISTS escalated_at TIMESTAMP WITH TIME ZONE,
ADD COLUMN IF NOT EXISTS escalated_by UUID REFERENCES auth.users(id);
-- Add index for escalated submissions
CREATE INDEX IF NOT EXISTS idx_content_submissions_escalated
ON public.content_submissions(escalated)
WHERE escalated = TRUE;
-- Add index for escalated_by
CREATE INDEX IF NOT EXISTS idx_content_submissions_escalated_by
ON public.content_submissions(escalated_by);
-- Add comments for documentation
COMMENT ON COLUMN public.content_submissions.escalated IS 'Whether this submission has been escalated to admin';
COMMENT ON COLUMN public.content_submissions.escalation_reason IS 'Reason for escalation';
COMMENT ON COLUMN public.content_submissions.escalated_at IS 'Timestamp when submission was escalated';
COMMENT ON COLUMN public.content_submissions.escalated_by IS 'User who escalated the submission';

15
supabase/migrations/20250930183452_6626976f-214b-4eee-a50c-f6c61be19e32.sql
View File

@@ -1,15 +0,0 @@
-- The content_submissions table already has RLS policies defined
-- We just need to ensure RLS is enabled (it should already be enabled from previous migrations)
-- This migration verifies RLS is enabled
-- Verify RLS is enabled on content_submissions
ALTER TABLE public.content_submissions ENABLE ROW LEVEL SECURITY;
-- Verify all existing RLS policies are in place
-- (They should already exist from previous migrations, but we document them here)
-- Users can create submissions (already exists)
-- Users can view their own submissions (already exists)
-- Moderators can view all content submissions (already exists)
-- Moderators can update content submissions (already exists)
-- Moderators can delete content submissions (already exists)