Local <--> Remote Migrations Help
I'm running into some issues with writing migrations.
I want to insert some data into the db to test a few features.
I want this data to be both on production database AND the local database.
So I'm doing this:
- Writing a miration to insert the data
-
However, since the migration is inserting data that depends on seed data (the user uuid),
running
I get around this by running supabase migration up instead.
- I then push this migration to the remote db with
- I then generate a new seed.sql file from the remote db state with:
- However, the problem I'm encountering is that the migration that inserts the data will still cause conflicts when running
- Fundementally, it seems like this is because the environments of the remote and local are different.
- The remote db already has seed data before running the latest migration
- But the local db has to run all migration first before seeding data.
- This leads to issues like the one I'm encountering.
I want to insert some data into the db to test a few features.
I want this data to be both on production database AND the local database.
So I'm doing this:
- Writing a miration to insert the data
-
supabase migration upsupabase db resetsupabase db resetHowever, since the migration is inserting data that depends on seed data (the user uuid),
running
supabase db resetI get around this by running supabase migration up instead.
- I then push this migration to the remote db with
supabase db push- I then generate a new seed.sql file from the remote db state with:
- However, the problem I'm encountering is that the migration that inserts the data will still cause conflicts when running
supabase db reset- Fundementally, it seems like this is because the environments of the remote and local are different.
- The remote db already has seed data before running the latest migration
- But the local db has to run all migration first before seeding data.
- This leads to issues like the one I'm encountering.
