tyler
ba94d755fa
- Update supabase/push-migrations.js: - Detect modern Supabase CLI link state (supabase/.temp/project-ref) - Prefer `supabase db query --linked --file` (works in this env where direct postgres connections fail with ENOTFOUND/network unreachable) - Updated docs/comments for `supabase login` + `supabase link --project-ref wnzkhezyhnfzhkhiflrp` workflow - Add MEMORY.md capturing the Supabase login/link session, tooling changes, migration patches applied, and gotchas - Patch migrations for current remote schema (column drift, syntax, idempotency, pre-existing tables): - 091_brand_plan_tier.sql: fix extra paren in get_brand_plan_info - 145_create_product_images_bucket.sql: allowed_mime_types + DROP POLICY IF EXISTS + safer bucket insert - 148_public_stops_rpc.sql: quote reserved "time" column in RETURNS TABLE + SELECT - 200_production_features.sql: add ALTER TABLE for user_activity_logs (originated in 036) so policies/indexes validate - 201_seed_data.sql: trim demo seeds with outdated column lists (products/stops/etc.); keep only compatible brands insert - Include 202_fix_admin_create_stop.sql and related stop creation updates (src/actions/stops/create-stop.ts, 147_admin_create_stop_rpcs.sql, ADMIN_CREATE_STOP_FIX.sql) - Update CLAUDE.md with pointer to MEMORY.md for recent migration work Applied via the new flow (after supabase login + link): 084, 091, 142–148, 200–202 etc. Refs: Supabase CLI now linked; use `node supabase/push-migrations.js <prefix>` or `npm run migrate:one NNN`
93 lines
2.5 KiB
PL/PgSQL
93 lines
2.5 KiB
PL/PgSQL
-- ============================================================================
|
|
-- Grok Fix Prompt: admin_create_stop (copy-paste ready for Supabase SQL Editor)
|
|
-- ============================================================================
|
|
-- This is the exact "Best Practice Version" from the fix prompt, with
|
|
-- additional comments. Run this directly in the Supabase SQL Editor
|
|
-- (https://supabase.com/dashboard/project/wnzkhezyhnfzhkhiflrp/sql) if the
|
|
-- migration push cannot be used.
|
|
--
|
|
-- After running, PostgREST may need a schema reload:
|
|
-- NOTIFY pgrst, 'reload schema';
|
|
--
|
|
-- Then test "Add New Stop" again.
|
|
--
|
|
-- The calling code (JS/TS) is in:
|
|
-- src/actions/stops/create-stop.ts (the fetch to /rest/v1/rpc/admin_create_stop)
|
|
-- src/components/admin/AddStopModal.tsx
|
|
-- src/components/admin/NewStopForm.tsx
|
|
-- (all go through the server action createStop which builds the p_* args)
|
|
-- ============================================================================
|
|
|
|
CREATE OR REPLACE FUNCTION public.admin_create_stop(
|
|
p_active boolean,
|
|
p_address text,
|
|
p_brand_id uuid,
|
|
p_city text,
|
|
p_cutoff_time time,
|
|
p_date date,
|
|
p_location text,
|
|
p_state text,
|
|
p_time time,
|
|
p_zip text
|
|
)
|
|
RETURNS jsonb
|
|
LANGUAGE plpgsql
|
|
SECURITY DEFINER
|
|
SET search_path = public
|
|
AS $$
|
|
DECLARE
|
|
new_stop_id uuid;
|
|
BEGIN
|
|
INSERT INTO stops (
|
|
active,
|
|
address,
|
|
brand_id,
|
|
city,
|
|
cutoff_time,
|
|
date,
|
|
location,
|
|
state,
|
|
time,
|
|
zip
|
|
)
|
|
VALUES (
|
|
p_active,
|
|
p_address,
|
|
p_brand_id,
|
|
p_city,
|
|
p_cutoff_time,
|
|
p_date,
|
|
p_location,
|
|
p_state,
|
|
p_time,
|
|
p_zip
|
|
)
|
|
RETURNING id INTO new_stop_id;
|
|
|
|
RETURN jsonb_build_object(
|
|
'success', true,
|
|
'stop_id', new_stop_id,
|
|
'message', 'Stop created successfully'
|
|
);
|
|
EXCEPTION WHEN OTHERS THEN
|
|
RETURN jsonb_build_object(
|
|
'success', false,
|
|
'error', SQLERRM
|
|
);
|
|
END;
|
|
$$;
|
|
|
|
-- Important: grant so PostgREST (anon key from server action) can invoke it.
|
|
GRANT EXECUTE ON FUNCTION public.admin_create_stop(
|
|
boolean, text, uuid, text, time, date, text, text, time, text
|
|
) TO anon, authenticated, service_role;
|
|
|
|
-- Reload cache so the function is immediately visible (avoids PGRST202).
|
|
NOTIFY pgrst, 'reload schema';
|
|
|
|
-- NOTE: The above simple version may fail on INSERT because the stops table
|
|
-- requires "slug" and "status" (NOT NULL, no defaults in all cases).
|
|
-- Prefer the enhanced version in migrations/202_fix_admin_create_stop.sql
|
|
-- which includes slug generation and status='draft' while using a compatible
|
|
-- signature and the success/stop_id return shape.
|