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 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.
cpan App::Sqitch DBD::Pg
cpan App::Sqitch DBD::SQLite
cpan App::Sqitch DBD::Oracle
cpan App::Sqitch DBD::mysql
cpan App::Sqitch DBD::Firebird
brew tap theory/sqitch
brew install sqitch_pg
brew install sqitch_sqlite
brew install sqitch_oracle
brew install sqitch_mysql
brew install sqitch_firebird
- Install ActivePerl
ppm install App-Sqitch
- For Oracle support, also run
ppm install DBD-Oracle
- For Firebird support, also run
ppm install DBD-Firebird
The documentation includes an tutorial for each database engine demonstrating the creation, development, and maintenance of a database with Sqitch.
Need help? subscribe to the mail list.
Sane Database Change Management with Sqitch
A one hour technical introduction to Sqitch, with detailed usage examples to help get you started.
Agile Database Development
Three hour technical tutorial originally presented at PGCon 2013 and updated in January 2014, covering source code control with Git, database change control with Sqitch, and test-driven database development with pgTAP.