rake is a strong model for how to make changes to a database. Every action has a build and teardown defined, which allows a lot of flexibility in determining what changes to make to a schema in a very modular way...just specify a desired end state and all of the objects know how to get themselves there.
Is it worth using this design pattern in our own build/teardown code? Pros/cons?
jthandy
commented
8 years ago
rake is a strong model for how to make changes to a database. Every action has a build and teardown defined, which allows a lot of flexibility in determining what changes to make to a schema in a very modular way...just specify a desired end state and all of the objects know how to get themselves there.
Is it worth using this design pattern in our own build/teardown code? Pros/cons?
cc @cmerrick and @drewbanin