Regarding branching
I was using the main branch till now, but as I have some major updates so I thought of creating a branch so that live data doesn't get effected, but when I created a new branch from supabase dashboard it didn't reflect some of my tables also didn't reflect some columns of the tables
4 Replies
Here I've an old migration file in my supabase_migration schema, How can i delete or update that
Going back slightly, how are you doing the branching, using github or using the supabase UI?
if the migration files in your supabase_migrations are incorrect then you usually have to revert it/
If you run
supabase migration list in the cli and send the screenshot, it will provide some details about how your migration is doingYeah, I did it using supabase UI, and yes there was a file in supabase_migration, I some how managed to repair it, but it took me to another bigger problem, the file got updated with the lates schemas but, there's http extension which is being used in some function, which gets initialised in the migrations file but at some point in the migrations file there's a DROP command for "drop type 'public'.'http_request'" and this gets failed while running the migrations..
How did you repair it? Could you not remove the DROP command? Would you be able to share a screenshot of what your migrations currently looks like in th ui and the errors you are getting from the logs from your branch.