From 66c4e942607e958d236b39c24df0109fb91bb3d5 Mon Sep 17 00:00:00 2001 From: Han Qiao Date: Mon, 2 Dec 2024 14:23:35 +0800 Subject: [PATCH] chore: update docs for remote db reset --- docs/supabase/db/reset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/supabase/db/reset.md b/docs/supabase/db/reset.md index 98a8003ca..3e224880b 100644 --- a/docs/supabase/db/reset.md +++ b/docs/supabase/db/reset.md @@ -6,4 +6,4 @@ Requires the local development stack to be started by running `supabase start`. Recreates the local Postgres container and applies all local migrations found in `supabase/migrations` directory. If test data is defined in `supabase/seed.sql`, it will be seeded after the migrations are run. Any other data or schema changes made during local development will be discarded. -Note that since Postgres roles are cluster level entities, those changes will persist between resets. In order to reset custom roles, you need to restart the local development stack. +When running db reset with `--linked` or `--db-url` flag, a SQL script is executed to identify and drop all user created entities in the remote database. Since Postgres roles are cluster level entities, any custom roles created through the dashboard or `supabase/roles.sql` will persist between remote resets.