Querydsl VS bytebase

There is a bit of tooling needed but is already around. For Java for example I had very good experience with a combination of flyway [1] for migrations, testcontainers [2] for making integration tests as easy as unit tests and querydsl [3] for a query and mapping layer.

[1] https://github.com/flyway/flyway

[2] https://java.testcontainers.org/modules/databases/postgres/

[3] https://github.com/querydsl/querydsl

http://querydsl.com/ also seems similar

As for JPA: I cannot miss the QueryDSL library for building typesafe queries. Another interesting alternative is Jinq, that provides a java stream api to query entities.

> all I really want is a nice API for building queries (that actually supports all underlying database features) and automatic mapping of the results to whatever objects/structs and primitives the language supports.

For Java based solutions, check out https://www.jooq.org/ or http://querydsl.com/

QueryDsl -- http://querydsl.com

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.