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
I read the README. I've talked to colleagues. And it is not clear why one would need to use this gem.
The DB schema is in schema.rb or structure.sql. This is the definitive source. New developers will load this or new copys of the DB will load this.
Existing devs will run the migrations but, after a certain amount of time, all devs will be up-to-date for a given set of migrations. These can be deleted.
With this gem these are deleted but also moved into a new an "init" migration. Now the project has 2 sources and a new version number every time migrations are squashed. This new version number contains entities that have already been applied to the DB and exist in schema.rb or structure.sql.
Why would one ever need to move unused migrations into a new init migration? Please explain. No one else can and I am lost 🧭
The text was updated successfully, but these errors were encountered:
I read the README. I've talked to colleagues. And it is not clear why one would need to use this gem.
The DB schema is in
schema.rb
orstructure.sql
. This is the definitive source. New developers will load this or new copys of the DB will load this.Existing devs will run the migrations but, after a certain amount of time, all devs will be up-to-date for a given set of migrations. These can be deleted.
With this gem these are deleted but also moved into a new an "init" migration. Now the project has 2 sources and a new version number every time migrations are squashed. This new version number contains entities that have already been applied to the DB and exist in
schema.rb
orstructure.sql
.Why would one ever need to move unused migrations into a new init migration? Please explain. No one else can and I am lost 🧭
The text was updated successfully, but these errors were encountered: