Declarative database schema migrations – yay or nay?

3 hours ago 1

Two issues I observed with typical migration as a separate new SQL file approach:

* Views don't have alter, so have to be fully redefined. Any change to a view obscures actually changed parts of a view, since you have to fully redefine it.

* Duplicate change tracking with git and migration history. Can't we just use git for history?

E.g. https://atlasgo.io/. Totally non affiliated with them. Just had a shower idea, but saw it already being implemented (yay).

Read Entire Article