Creator of https://xitter.cf/t.co/xIYXP18EYH, a CLI for managing schema changes.

San Francsico, CA
Joined March 2007
You Either Die A Hero, Or You Live Long Enough To See Yourself Become The Villain — Harvey Dent Obviously he was referring to open-source projects..
1
1
21
This release improves state lookup against tools that return json, and other minor improvements. In our limited test data (80 pipeline runs, same model, two weeks either side), we're seeing a 33% drop in turns and a 47% drop in context tokens in the resolve step. YMMV.
1
24
If a later table or column rename is recorded in the log, retrofit will create the snapshot with renames, datasets do not need to be recaptured with the new names. This works because when we capture the dataset, we also note where in the change history it was captured.
1
8
Don’t forget to sign up on the site for announcements about early access.
3
So a migration between the two points in the schema history will result in a script that only applies the changes (adding the new currency to the currency table). A downgrade will just remove the record(s).
1
5
If a column or table is renamed that holds the reference data you don’t need to capture it again, the renames will be applied when the snapshot or migration script is rendered.
2
There are a lot of different strategies to manage this data in migration scripts and data files. Retrofit can capture reference data and pin it to a specific version of your schema. By default, it is included when rendering a snapshot or migration script.
1
17
If witnessed and sealed, the data cannot ship if changed underneath, retrofit will detect the edit and refuse. Additions (or updates) to the reference table are captured in a new file and pinned against the current DDL version.
1
8
Reference data is the data that apps only read, and never write, like zip codes and states. This includes data that might change slowly over time, like an order status label, or even currencies.
1
1
27
The win is when you broker all your changes through retrofit, it will render the forward and reverse migration scripts for you that Ruby can run like it always has. One less thing to worry about since Ruby handles so much already but punted the risky stuff back to the developer.
1
2
43
Check out our extended homepage content to learn how retrofit can help you and your team especially with managing risk where other tools leave gaps. Plus, even stronger support for migration reversal in the coming weeks.
1
1
31
As always, we welcome your feedback and requests. The repo is available for early access users.
17
Hey all It’s Wednesday and we have a new retrofit demo to share: retrofit.sh/demos/rails-adop… This is similar to the Liquibase and Flyway demos. We inject retrofit into the Ruby/Rails developer workflow. Bootstrapping an existing Ruby project into retrofit is quite trivial.
2
3
99
Finally we merge (rebase!) all the branches, confirm there were no structural conflicts during the merges, and again test the combined up and down migrations. If you or anyone on your team would be interested in getting early access, have them sign up on our website.
1
34
Please share! Also, I’m not sure what we can pull off, but making reference data (data in tables your application only reads) first class and versioned with the schema is one of the harder problems we are currently designing and testing. Hope to have a demo of that soon.
15