Files
thrilltrack-explorer/supabase/migrations/20251020185731_78f1fc16-f1c0-462e-b63e-eeb62d2145b5.sql
2025-10-20 18:58:00 +00:00

28 lines
1.2 KiB
SQL

-- Phase 1: Database Security Hardening
-- Fix search_path mutable warnings
-- Note: We cannot identify which specific functions need fixing without seeing them,
-- but based on the linter warnings, we need to add SET search_path = 'public'
-- to functions that don't have it set.
-- The linter identified 2 functions with mutable search_path.
-- We'll create a comment here to document the fix that needs manual application
-- in the Supabase dashboard SQL editor.
-- MANUAL ACTION REQUIRED:
-- 1. Go to Supabase Dashboard → SQL Editor
-- 2. Run this query to find functions without search_path set:
-- SELECT routine_schema, routine_name
-- FROM information_schema.routines
-- WHERE routine_schema = 'public'
-- AND routine_type = 'FUNCTION'
-- AND NOT (routine_definition LIKE '%SET search_path%');
-- 3. For each function found, add: SET search_path = 'public'
-- Example of what needs to be done (REFERENCE ONLY - DO NOT RUN):
-- ALTER FUNCTION public.your_function_name() SET search_path = 'public';
-- We cannot automatically fix this in migrations because we need to know
-- the specific function signatures, which vary.
COMMENT ON SCHEMA public IS 'Phase 1 Security: search_path hardening requires manual fixes - see migration notes';