tern VS goose

We have a repo with migrations written in SQL, and we use tern[1] to apply them.

[1]: https://github.com/jackc/tern

If you are using postgres and pgx you may want to use tern.

Recently i started using turn its more fun (IMPO) compared to others tool available https://github.com/jackc/tern

We use https://github.com/jackc/tern library (from the author of the pgx driver). We run migrations in k8s init containers and we do not do rollbacks (only up). Advantages over other popular solutions are:

I’ve been happy with https://github.com/jackc/tern .

I use tern for migrations. It’s from the same Author as pgx so everything in that ecosystem plays well.

Now my next issue is I'm trying to install tern using the "go versions 1.17 and higher" instructions in the docs here https://github.com/jackc/tern

I use https://github.com/jackc/tern + .env files which interpolate with its config for various environments.

Tern is a great language and framework agnostic solution for SQL migrations https://github.com/jackc/tern

In v3.16.0 we added a new Provider feature that unlocks the ability to implement a lot of highly requested features. More details in the blog post:

Next try https://github.com/pressly/goose We have this setup to be run by the CI-CD pipeline to be run before the application is started. BTW, this utility is compatible with https://sqlc.dev , so they work good together.

For database migration I recommend https://github.com/pressly/goose As it works with sqlc and is a powerful tool for complex migrations. This is something a lot of ORMs are really weak with. I was on a large project with Gorm as the ORM and what a nightmare when we pushed to production!

goose https://github.com/pressly/goose - data migration and seed data creation

I'm using .sql migration files with tooling similar to https://github.com/pressly/goose . Is there a way to manage my schema with my pre-existing tooling and my queries/CRUD operations with Ent/Atlas?