Sqitch is not integrated with any framework, ORM, or platform. Rather, it is a standalone change management system with no opinions about your database engine, application framework, or your development environment.
Database changes may declare dependencies on other changes--even on changes from other Sqitch projects. This ensures proper order of execution, even when you've committed changes to your VCS out-of-order.
Change deployment is managed by maintaining a plan file. As such, there is no need to number your changes, although you can if you want. Sqitch doesn't much care how you name your changes.
Up until you tag and release your application, you can modify your change deployment scripts as often as you like. They're not locked in just because they've been committed to your VCS. This allows you to take an iterative approach to developing your database schema. Or, better, you can do test-driven database development.
If you're using a VCS to track your changes, you don't have to duplicate entire change scripts for simple changes. As long as the changes are idempotent, you can change your code directly, and Sqitch will know it needs to be updated.
cpan App::Sqitch DBD::Pg
cpan App::Sqitch DBD::SQLite
cpan App::Sqitch DBD::Oracle
brew tap theory/sqitch
brew install sqitch-pg
brew install sqitch-sqlite
brew install sqitch-oracle
- Install ActivePerl
ppm install App-Sqitch
- For Oracle support, also run
ppm install DBD-Oracle
The documentation includes an tutorial for each database engine demonstrating the creation, development, and maintenance of a database with Sqitch.
Video of “Sane Database Change Management with Sqitch.” Presented to the Portland PostgreSQL Users Group in September, 2012.
From “Sane Database Change Management with Sqitch.” Presented to the Portland Perl Mongers in January, 2013.