From d62b17ad65a786f6c64a55f6dbecbe38b9744ca6 Mon Sep 17 00:00:00 2001
From: Josh Creek <8179928+jcreek@users.noreply.github.com>
Date: Sat, 2 Nov 2024 15:38:13 +0000
Subject: [PATCH] docs(#55): Improve clarity around db migrations

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
---
 docs/database-setup.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/database-setup.md b/docs/database-setup.md
index 227279a..5ee424d 100644
--- a/docs/database-setup.md
+++ b/docs/database-setup.md
@@ -83,6 +83,8 @@ To do so without resetting the database, you can use the following command:
 
 `npx supabase migration up`
 
+> Use this command when you want to preserve existing data whilst applying new schema changes. For a fresh start with test data, use `npx supabase db reset` instead.
+
 And for the database in the cloud:
 
 `npx supabase db push`