Full migration + data on Branch
Trying to figure out the best way to track schema and rpc function changes so we are looking at separate projects vs. branches.
Attempting to set up a branch has been a nightmare. The supabase produced migration files have storage triggers written into the migration query that breaks the migration. That alone is a question in its own right. But, beyond that, how am I to get data seeded over when creating a branch? In what world would an actual production team be testing db changes without data?
I cannot use the CLI to seed because we have dns issues with the IPv4 proxy so I need a solution in the studio. Otherwise, while our main project db is configured to be IPv4 compatible, branches don't inherit this (another insane issue).
So, how can I seed my branch from the studio?
This is as much of a rant as it is a question. For as many things as I've really liked about supabase, I'm at an equal level of disdain for it.
Attempting to set up a branch has been a nightmare. The supabase produced migration files have storage triggers written into the migration query that breaks the migration. That alone is a question in its own right. But, beyond that, how am I to get data seeded over when creating a branch? In what world would an actual production team be testing db changes without data?
I cannot use the CLI to seed because we have dns issues with the IPv4 proxy so I need a solution in the studio. Otherwise, while our main project db is configured to be IPv4 compatible, branches don't inherit this (another insane issue).
So, how can I seed my branch from the studio?
This is as much of a rant as it is a question. For as many things as I've really liked about supabase, I'm at an equal level of disdain for it.
