Dat VS Sqitch

Yes there are some really interesting projects, also in the ML replicability space. One really nice approach is the DAT project [1]. The protocol [2] looks pretty sensible and useful. Unfortunately, the tooling has been in such a state of permanent flux (i.e. Perpetual deprecation) that I've never bothered to invest much time. [1] https://datproject.org/ [1] https://datproject.org/. - Source: Hacker News / about 2 years 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 / 19 days 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