goose VS bytebase

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?

We have been building https://github.com/bytebase/bytebase for 3+ years. You can think it of as GitHub/GitLab for SQL changes, with integrated GitOps, code review and deployment.

You can further check out this tutorial to get a feel of our GitOps solution

https://www.bytebase.com/docs/tutorials/database-change-mana...

We have been working on bytebase (https://github.com/bytebase/bytebase) for 3+ years to address this. With a change review workflow, environment propagations, and try not to disturb the dev flow if possible.

Migrations. All my database logic lives in version control.

Popular tooling like Phoenix, Hasura, etc have good built in migration stories.

https://www.bytebase.com looks really promising.

Hover, I do struggle with one big issue: changing database logic (views, functions, etc) that has other logic dependent on it. This seems like a solvable problem.

bytebase.com — Database CI/CD and DevOps. Free under 20 users and ten database instances

Bytebase offers a powerful GUI for schema migration deployments. This tutorial will show you how to use Bytebase to deploy schema migrations with features like SQL Review, custom approval, time scheduling, and more.

Now there are more subdivided practice: * Policy as Code: Sentinel, OPA * Database as Code: bytebase * AppConfiguration as Code: KusionStack, Acorn * ...... (Welcome to add more)

Bytebase is an open-source Database DevOps and CI/CD tool for teams, designed to centralize the control and secure your organization’s most valuable asset, the database data.

I use Bytebase to manage database changes for MySQL with GitOps workflow. I can manage my SQL scripts in my GitLab repo, and trigger a database change issue with committing a MR. Then Bytebase will record it after the issue is executed successfully. But I am not sure whether it supports procedures. Refer to https://github.com/bytebase/bytebase to get more details.