Ad-hoc migrations with no versioning
This post describes a new feature recently added to goose
-- the ability to apply migrations with
no versioning. A common use case is to seed a database with data after versioned migrations
have been applied.
This post describes a new feature recently added to goose
-- the ability to apply migrations with
no versioning. A common use case is to seed a database with data after versioned migrations
have been applied.
A while ago a co-op student, who happened to be a visual leaner, asked if it were possible to
explain goose
commands visually. At the time we were still at an office, so we gathered around the
whiteboard and doodled some diagrams.
This post captures some of those whiteboard sketches, which seemed to help.
Starting with goose
v3.3.0 we added the
ability to apply missing (out-of-order) migrations. Thanks for all the the community feedback over
the years.