Sane Database Change Management with Sqitch*
SQL change management has always sucked. This talk introduces Sqitch, the SQL change management application that doesn’t suck. Come see how it works, learn the few simple rules you need to get the most out of it, and liberate yourself from the suckitude.
SQL change management is hard. Most database “migration” systems require opaque naming conventions, prefer DSLs that cover a fraction of SQL, and require duplication of code for simple changes to existing functions. Such does not have to be. And now it’s not.
Introducing Sqitch, simple SQL change management that doesn’t suck. Sqitch doesn’t care what programming language your app is written in. It has no opinions as to what database to use or what its schema should look like. And it doesn’t require sequentially-named migration scripts or the use of any DSL other than SQL. Sqitch lets you to write SQL migration scripts thar target your database, and provides a simple, unintrusive interface for specifying dependencies, so that it can run things in the proper order.
So come to this talk to learn all about Sqitch: How it works, where to get it, and how to get the most out of managing database deployments.
database, SQL, vcs, version-control
I've spoken at Open Source Bridge, OSCON, pgCon, and before numerous open-source user groups.
David Wheeler is Chief Yak Barber at iovation and an associate at PGExperts. He’s responsible for PGXN‘, the PostgreSQL Extension Network, pgTAP, a PostgreSQL test framework, and Sqitch, a database change management app. He’s into testing and extension distribution, and baking artisan bread with wild yeast.