| Thank you for the helpful feedback. > Using supabase migration up would mean moving the latest migration out of the migrations folder, running supabase db reset, moving the file back in and then calling supabase migration up. We can definitely do a better job here. I'm adding support for db reset --version flag [0]. This should allow you run migration up without moving files around directories. > I wasn't really sure what the actual outcome would look like If I have something like this in a migration script Agree that we can do a better job with the documentation for squash command. I will add more examples. The current implementation does a schema only dump from the local database, created by running local migration files. Any insert statements will be excluded from the dump. I believe this is not the correct behaviour so I've filed a bug [1] to fix in the next stable release. [0] https://github.com/supabase/cli/pull/1369 [1] https://github.com/supabase/cli/issues/1370 |