Bytebase VS Sqitch

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. - Source: dev.to / 4 months ago

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... - Source: dev.to / 7 months ago

Bytebase could be a fit. It provides a GitLab like experience for teams to coordinate database changes. Source: 11 months ago

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

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. Source: 11 months ago

We use https://sqitch.org/ and we’re fairly happy with it. Sqitch manages the files to deploy which are applied fits to a local database. We use GitHub actions for deployment and database migrations are just one step of the pipeline. The step invokes sqitch deploy which runs all the pending migration files. Then, all the approval process is standard for the environment. We require approvals in pull requests... - Source: Hacker News / about 1 month ago

I'm experimenting with it right now using Squitch [1] to make maintenance easier. It still feels like a hack and I also still have my doubts about the viability of this for real-world use. It's fun though and I'm learning about all kinds of advanced Postgres features. [1] https://sqitch.org/. - Source: Hacker News / 5 months ago

How does it compare with other SQL-based migration tools like Sqitch? Source: about 1 year ago

Yup, same. Last time I set this up I used Sqitch¹ for migrations, which encourages you to write tests for each migration; caught a lot of bugs early that way, all in a local-first dev environment. Worked especially well for Postgres since plpgsql makes it easy to write tests more imperatively. ¹: https://sqitch.org/. - Source: Hacker News / over 1 year ago

Sqitch. DB migrations for multiple data stores without a proprietary syntax for DB updates. Git-aware. Integrated unit testing. Https://sqitch.org/ Https://youtu.be/wF4PEe8HD7k. Source: over 1 year ago