bytebase.com VS renovate

Bytebase is an open-source database DevOps tool, it's the GitLab/GitHub for managing databases throughout the application development lifecycle. It offers a web-based collaboration workspace for DBAs, Developers and platform engineers. It consolidates disparate DB tools such as DBeaver, Liquibase, Flyway into a single place.

Or bytebase.com which has a GUI.

If you like this tutorial, you might also be interested in our product Bytebase, an open-source, web-based schema change management tool, that helps you manage ClickHouse database, supporting SQL review, version control, backup and restore etc...

bytebase could be a fit. It provides a GitLab like experience for teams to coordinate database changes.

You may check a more modern tool bytebase.com. GUI-based, GitOps native, plus an embedded SQL query tool ...

For database structure, you may try bytebase.com, whose GitOps workflow could work for you even for the free version. It also has a GUI to trace and approve changes, a query editor and etc.

Thanks! Yeah definitely agree that building out declarative table management for Postgres would be a major effort. A few open source projects I've seen in that area include:

https://github.com/sqldef/sqldef (Go)

https://github.com/bikeshedder/tusker (Python but being ported to Rust)

https://github.com/tyrchen/renovate (Rust)

https://github.com/blainehansen/postgres_migrator (Rust)

Some of these are based on parsing SQL, and others are based on running the CREATEs in a temporary location and introspecting the result.

The schema export side can be especially tricky for Postgres, since it lacks a built-in equivalent to MySQL's SHOW CREATE TABLE. So most of these declarative pg tools shell out to pg_dump, or require the user to do so. But sqldef actually implements CREATE TABLE dumping in pure Golang if I recall correctly, which is pretty cool.

There's also the question of implementing the table diff logic from scratch, vs shelling out to another tool or using a library. For the latter path, there's a nice blog post from Supabase about how they evaluated the various options: https://supabase.com/blog/supabase-cli#choosing-the-best-dif...

If it looks interesting to you, here's the repo with more details: https://github.com/tyrchen/renovate.