Version Control Integration
Sqitch integrates seamlessly with version control systems, allowing for a more structured and traceable database change management process. Each change is associated with a VCS change, making it easier to track and revert changes.
Script-based Approach
It uses a script-based approach rather than a state-based one, which provides more flexibility and control over the changes being applied to the database. This method makes it easier to handle complex and non-linear migrations.
Multi-engine Support
Sqitch supports various database engines such as PostgreSQL, MySQL, Oracle, SQLite, and more, making it versatile and applicable to a wide range of projects.
No Requirement for a Dedicated Server
Unlike some migration tools, Sqitch does not require a dedicated database server for tracking schema changes, simplifying the deployment process.
Dependency Management
It allows setting dependencies between changes, ensuring that changes are applied in the correct order and preventing potential issues related to dependency conflicts.
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 / 11 months 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 / over 1 year ago
How does it compare with other SQL-based migration tools like Sqitch? Source: about 2 years 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 / about 2 years 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 2 years ago
There are attempts to change the way SQL stuff is handled to make it closer to other development processes, such as tSQLt for testing or Sqitch for git-like schema changes, etc. They are there for a reason, to improve your workflow if you cannot get rid of those mammoth SQL codebase. Use those kind of tools as much as you can. Source: over 2 years ago
Since your existing transformation queries are written in SQL and orchestrated by Airflow, then you could write your DDL queries together with a database migration tool, for example: Sqitch, Flyway, and Liquidbase (there's probably more I'm missing). Source: over 2 years ago
I recently saw some very enthusiastic endorsements of https://sqitch.org/ - I tried it out myself and it seemed very well designed and ticked all of my boxes, but I've not used it for a full project yet. Source: over 2 years ago
An alternative would be https://sqitch.org/. Source: over 2 years ago
> ad-hoc SQL functions in the database If you use tools like Sqitch, Metagration or any other suitable migration management system then functions in your database stop being scary. Sqitch: https://sqitch.org/. - Source: Hacker News / almost 3 years ago
For database migrations, I almost exclusively use sqitch. Source: almost 3 years ago
Probably I misunderstood the problem, but did you check https://sqitch.org. Source: almost 3 years ago
You can also use a tool like Sqitch which helps you manage migration separately. However you can't generate changes from your code, which is one of the main selling point of EF. Source: about 3 years ago
Https://sqitch.org/ might be of interest. Source: about 3 years ago
Use your standard DB migration tooling, with code/change review as part of the process. I’m a big fan of sqitch[1] but many migration tools will handle data updates as well as DDL. 1: https://sqitch.org/. - Source: Hacker News / over 3 years ago
Have you seen Sqitch (https://sqitch.org/)? It does exactly this, and it's a battle-tested system with a decent number of users, and it supports many database. I didn't dig deep into this new system, but it looks very much like Sqitch at a glance. - Source: Hacker News / over 3 years ago
I am also aware that there are other tools, such as sqitch, available for helping manage database changes in a way that makes it easier to track the history of changes. I have not tried such tools myself, but may look into them in the future. It may be preferable to use tools like this if recreating the schema completely is too slow, or there are changes for which you can't just simply recreate the schema entirely. - Source: dev.to / over 3 years ago
Do you know an article comparing Sqitch to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Sqitch. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.