Sane Database Change Management with Sqitch*
Database 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.
Database change management is hard. Most “migration”-style implementations 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.
I have been speaking at open-source conferences and for regional user groups since 2003. My most recent gigs have been given this very talk to PDXPUG ("video":https://vimeo.com/50104469), and an earlier version at "PGCon":http://www.pgcon.org/2012/schedule/events/479.en.html last year. In the past, I have also presented on test-driven database development, notably at "osb2009":http://opensourcebridge.org/sessions/43.
iovation; PG Experts