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
Is your feature request related to a problem? Please describe.
When working with more complicated databases with views, functions and temporary tables, it would be good to have the drop command clean those up as well. I'm mostly using the drop command in development and test environments and the drop command has been great for cleaning things out and starting fresh.
I've recently introduced functions and views to the database schema to take advantage of some of the more powerful features of PostgreSQL. Migrating up and down works fine with creating and cleaning up these types of objects, but if a migration fails during development or testing I can't use the drop command to clean up and start fresh.
As a workaround I have been deleting the database or cleaning up my PostgreSQL container with a new volume
Describe the solution you'd like
It would be ideal if the Drop method for migrate supported all the types of objects that can be used in a migrate file, that way a user could easily get back to a clean slate in the case of a broken migration
Describe alternatives you've considered
Workaround is to delete the database and start over that way
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When working with more complicated databases with views, functions and temporary tables, it would be good to have the drop command clean those up as well. I'm mostly using the drop command in development and test environments and the drop command has been great for cleaning things out and starting fresh.
I've recently introduced functions and views to the database schema to take advantage of some of the more powerful features of PostgreSQL. Migrating up and down works fine with creating and cleaning up these types of objects, but if a migration fails during development or testing I can't use the drop command to clean up and start fresh.
As a workaround I have been deleting the database or cleaning up my PostgreSQL container with a new volume
Describe the solution you'd like
It would be ideal if the Drop method for migrate supported all the types of objects that can be used in a migrate file, that way a user could easily get back to a clean slate in the case of a broken migration
Describe alternatives you've considered
Workaround is to delete the database and start over that way
Additional context
The text was updated successfully, but these errors were encountered: