Pinned Tweet
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..
If you are looking to improve skill reliability and reduce turns when managing state transitions, check out our new release of intrastate.
github.com/cwensel/intrastat…
#llm
Continuing from last week's demo on reference data, this week we show off how we handle seed data.
retrofit.sh/demos/seed-data/
#postgreSQL #sql #llm
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.
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).
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.
Hey all
Finally, I think we landed on a great design with handling both reference (and seed) data in retrofit.
This week we demo managing reference data as part of the schema.
retrofit.sh/demos/reference-…
#postgreSQL #SQL
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.
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.
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.
Hey all
We have a new retrofit demo to share:
retrofit.sh/demos/manually-t…
Imagine your team has been using retrofit for the past couple weeks and now every branch to be reviewed has a schema change that will require a migration in production. grin
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.
