| > if your latest migration is destructive - you want to seed data and then run the next migration. We have added supabase migration up [0] command that runs only pending migrations (ie. those that don't exist in local db's migration history table). You can use that to test destructive migration locally with data from seed.sql. After testing, you want to update your seed.sql with a data-only dump [1] from your local db. That would make CI happy with both the new migration and the new seed file. > 2. run a preseed script that disables any triggers and removes default data that has been previously seeded in migrations It sounds like the default data is no longer relevant for your local development. If so, I would suggest running supabase migration squash [2] to remove the default data. To disable triggers before seeding data, you can add the following line to seed.sql [3] SET session_replication_role = replica; [0] https://supabase.com/docs/reference/cli/supabase-migration-u... [1] https://supabase.com/docs/reference/cli/supabase-db-dump [2] https://supabase.com/docs/reference/cli/supabase-migration-s... [3] https://stackoverflow.com/questions/3942258/how-do-i-tempora... |
I like being able to call supabase db dump (data only) and not touch code in the file at all - I get that adding SET session_replication_role = replica; is one line, but still my preference is to avoid. But like I said I already disable triggers ahead of the seed script running.
I currently use supabase db reset quite frequently as I make changes in development. 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. Which is not the worst idea, I'd still be looking to automate those steps with my own script atm tho.
Re: squash I have been a little cautious to use it since I first noticed it in the CLI docs as I wasn't really sure what the actual outcome would look like If I have something like this in a migration script:
--set initial permissions INSERT INTO rbac.permissions(name) SELECT unnest(enum_range(NULL::rbac.permission_name)) except SELECT name FROM rbac.permissions;
what would squash do to handle this data?