Fix live map community schema and refresh API cache
Some checks failed
Deploy MineGeo to Dokploy / deploy (push) Failing after 3m16s
Some checks failed
Deploy MineGeo to Dokploy / deploy (push) Failing after 3m16s
This commit is contained in:
@@ -10,6 +10,8 @@ Moderators and admins can remove comments directly on map pages or from **Commen
|
|||||||
|
|
||||||
Apply `supabase/migrations/20261017073500_map_community_features.sql` before deploying the application. This adds `map_reactions`, `map_comments`, `community_reports`, and `map_reaction_summary`. All tables enable RLS and restrict access to the server service role. Browser and device-token clients cannot directly read or write these tables. The server routes validate browser sessions, active account status, published-map visibility, and staff roles.
|
Apply `supabase/migrations/20261017073500_map_community_features.sql` before deploying the application. This adds `map_reactions`, `map_comments`, `community_reports`, and `map_reaction_summary`. All tables enable RLS and restrict access to the server service role. Browser and device-token clients cannot directly read or write these tables. The server routes validate browser sessions, active account status, published-map visibility, and staff roles.
|
||||||
|
|
||||||
|
If the server reports `PGRST205` for `public.map_comments`, verify that this migration was applied to the Supabase project configured by the deployed app. Deploying the application source does not apply database migrations. The migration also requests a PostgREST schema-cache reload. If the tables already exist but the cache remains stale, run `NOTIFY pgrst, 'reload schema';` in that project's SQL editor instead of rerunning the table-creation statements.
|
||||||
|
|
||||||
- `node --import tsx --test tests/community.test.ts` — validation, authentication, moderator authorization, scoped reactions, reporting and review conflicts.
|
- `node --import tsx --test tests/community.test.ts` — validation, authentication, moderator authorization, scoped reactions, reporting and review conflicts.
|
||||||
- `node scripts/test-community-sql.mjs` — applies the full migration history in isolated PGlite and verifies constraints, counts, duplicates, deletion, and privileges. Uses the same optional `.data/sql-verification` runtime as the existing SQL suites.
|
- `node scripts/test-community-sql.mjs` — applies the full migration history in isolated PGlite and verifies constraints, counts, duplicates, deletion, and privileges. Uses the same optional `.data/sql-verification` runtime as the existing SQL suites.
|
||||||
|
|
||||||
|
|||||||
@@ -64,3 +64,6 @@ language sql stable security invoker set search_path = '' as $$
|
|||||||
$$;
|
$$;
|
||||||
revoke all on function public.map_reaction_summary(uuid) from public, anon, authenticated;
|
revoke all on function public.map_reaction_summary(uuid) from public, anon, authenticated;
|
||||||
grant execute on function public.map_reaction_summary(uuid) to service_role;
|
grant execute on function public.map_reaction_summary(uuid) to service_role;
|
||||||
|
|
||||||
|
-- Make new tables and the RPC visible to PostgREST immediately after commit.
|
||||||
|
notify pgrst, 'reload schema';
|
||||||
|
|||||||
Reference in New Issue
Block a user