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
When collaborating on a project, there needs to be a proper way to handle "temporary" migrations. I use the system of calling the migrations on my feature branch new-001-whatever.sql, so I can go through and number them properly when merging the PR, but can this be automated by the migrate command?
Something I've noticed other developers doing is creating the change locally in their database, then pasting the generated DDL code into a new migration, but when it comes to running gt migrate, there's then a failure because their local database already has the tables created...
Something to think about for a rainy day...
The text was updated successfully, but these errors were encountered:
When collaborating on a project, there needs to be a proper way to handle "temporary" migrations. I use the system of calling the migrations on my feature branch
new-001-whatever.sql
, so I can go through and number them properly when merging the PR, but can this be automated by themigrate
command?Something I've noticed other developers doing is creating the change locally in their database, then pasting the generated DDL code into a new migration, but when it comes to running
gt migrate
, there's then a failure because their local database already has the tables created...Something to think about for a rainy day...
The text was updated successfully, but these errors were encountered: