Trying to understand supabase-cli migrations. Is there a way to start supabase without running existing migrations? I would like to keep a file with the whole schema [big sql file] around (so i can quickly inspect it). When making changes to database schema i have two options 1) hand written migration 2) change the full schema [big sql file] 2.1) run

psql -f schema.sql

against freshly started supabase instance 2.2) run a

supabase db changes

with 2.1 against a supabase with all existing migrations to get a diff 2.3) (check diff + update where necessary) apply diff to production to end up with a same state as in 2.1 currently when you run

supabase start

it seems to run all existing migrations so i can't easily execute 2.1) and i have to essentially hand write my migrations. Or is the intended workflow the other way around and i should not maintain a hand written

schema.sql

but instead do

pg_dump

of the final database to get it? But this would still mean i have to hand write migrations or do manual changes to the database (i prefer to do it in code).

Hello @pocin! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

i think i've read all the github issues blogposts/docs published by supabase but i am still going in circles trying to figure out a comfortable dev flow