Hello all,
I preserve miglite, a small migration device for Go initiatives that want plain SQL recordsdata. The v0.8.0 launch provides fs.FS assist, primarily for companies that wish to embed migrations with go:embed:
//go:embed migrations/*.sql
var migrationFS embed.FS
mig.SetFS(migrationFS).SetSqlDB(db)
The migration path is an io/fs logical path, and SetFS(nil) switches again to the native filesystem. The CLI instructions and file format keep unchanged.
The identical replace fixes three behaviours that have been simple to overlook: --skip-err now continues however returns a failure, injected *sql.DB values will not be closed by miglite, and a file with out DOWN is reported as skipped.
Particulars: Inhere’s Website • miglite v0.8.0: ship migrations contained in the binary
For small companies, how do you determine between embedding migrations and transport a separate listing? I might particularly respect suggestions on the fs.FS API.
