You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resetting the db naively will confuse pgmg, as roles will still exist in the cluster. So if you want to drop the db and re-run everything (say for tests) any create role command will fail because the role already exists.
I don't want to encourage wrapping these cluster level commands in a try catch. So maybe we provide a reset-db command that drops the application db, but then re-seeds the cluster pgmg records before running the migration.
Something to dogfood.
The text was updated successfully, but these errors were encountered:
Resetting the db naively will confuse pgmg, as roles will still exist in the cluster. So if you want to drop the db and re-run everything (say for tests) any create role command will fail because the role already exists.
I don't want to encourage wrapping these cluster level commands in a try catch. So maybe we provide a reset-db command that drops the application db, but then re-seeds the cluster pgmg records before running the migration.
Something to dogfood.
The text was updated successfully, but these errors were encountered: