liquibase VS bytebase

While I respect the work, Liquibase's code base is quite messy... https://github.com/liquibase/liquibase

Have you looked at liquibase?

For those in search of a open source solution with commercial support have a look at https://www.liquibase.org/

I haven't used it for a number of years but it sounds like something like liquibase (https://www.liquibase.org/) might be what you're looking for.

Liquibase

We use https://github.com/liquibase/liquibase, as most of Dev are used to and comfortable with it.

Highly recommend you use either Liquibase or Flyway for schema management, and Testcontainers pg to run a transitive database for your tests.

I haven't used this so I'm not sure it does exactly what you're looking for but I had a DBA recommend it to me as a possible tool to start using as we overhaul our pipelines. https://www.liquibase.org/

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.