So hmmm... I broke my DB (had some errors with mig...
# help
y
So hmmm... I broke my DB (had some errors with migrations and then was stupid enough to remove the
schema_migrations
table). It's still a dev version so I could reset the db completely. Is there to reset the remote db? I still have the proper migrations on my version control 🙂
s
I don't think there is a way for a user to reset the database (as in have all the schemas and tables set back to how they originally were). What you can do is delete that project and create a new one.
A rule of thumb is to not create, update or delete anything in schemas that you didn't create except for the
public
schema
y
@User Thanks. Creating a new project kinda sucks but if there are no other choices, then that's what it is 🤷🏻‍♂️ Will my migrations work on a new project without any issues?
s
I don't know what you are using to do your migrations
I use migrations for all my projects and have no issue
y
I used
supabase db remote commit
But I mean, will the current migration file for
project A
will work for
project B
s
Oh that I'm not too sure of, but you get 2 free projects in your organisation, so you could create
project B
while
project A
remain to test it out
y
Thanks!