Simple, minimal SQL database migrations written in Go with generics. Std lib database/sql and SQLX supported OOTB

7 points by ogg

I built GoSMig for personal projects and open-sourced it. It’s a tiny library for writing migrations in Go (compile-time checks via generics). Supports both transactional and non-transactional steps, rollback, status/version commands, and a built-in CLI handler so you can ship your own tool.

Zero dependencies (std lib; golang.org/x/term used for pager support)
database/sql and sqlx supported out of the box, others would work too
tested with PostgreSQL, other RDBMSs would work too

Repo: https://github.com/padurean/gosmig Examples: https://github.com/padurean/gosmig/tree/examples

Curious how this compares to your current workflow and what would make it adoptable at work.

sigmonsez

Are there any notable differences to existing migrate tools?

specifically what are the differences to goose, golang-migrate/migrate or ariga/atlas

ogg
It's mostly a subset of features of the existing tools. I created it after being annoyed while trying to find my way on how to use goose to build my own migration CLI with it with no plain SQL migrations - only with migrations written in Go (with sqlx), which are embedded in the migration binary, without any external dir containing SQL files.

So i built just that:
- only migrations written in Go (no plain SQL migration files)
- writing migrations with SQLX (or database/sql) just works, straight out of the box.
I also wanted to see if i could make use of Go's generics (which are sort of limited/incomplete) to achieve this.