Open rndquu opened 2 days ago
@gentlementlegen FYI
I am fixing current migrations because it seems that ubiquibot
repository is not up to date, at that point I am searching if any repo contains them or if everything was done through Supabase UI... After that we can add other migrations.
@rndquu I could not find these anywhere so I assume they all were applied via the UI without any backup or file. The init
sql combines all of these changes in one migration so it might be fine? Anyway feel free to add migrations (via migration files please) here. The problem is that the migration table will not match so migrations won't be applied except if also applied manually through Supabase UI.
@rndquu I could not find these anywhere so I assume they all were applied via the UI without any backup or file. The
init
sql combines all of these changes in one migration so it might be fine? Anyway feel free to add migrations (via migration files please) here. The problem is that the migration table will not match so migrations won't be applied except if also applied manually through Supabase UI.
I feel like we need to "hard reset" our DB:
I agree. Do these backup include triggers, functions, and other access changes?
I agree. Do these backup include triggers, functions, and other access changes?
Not sure. Do we use triggers and DB functions?
There are a few registered within the DB that are triggered on data changed, on CRON fashion. I do not know if they matter, not who created them.
There are a few registered within the DB that are triggered on data changed, on CRON fashion. I do not know if they matter, not who created them.
Updated description
Our DB has a few drawbacks:
It makes sense to recreate our existing DB from scratch using a single migration fetched from a DB backup.
This way:
What should be done: