January2013Meeting

Anthony Johnson edited this page May 16, 2013 · 1 revision

Sane Database Change Management with Sqitch

SQL 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 that 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.

David Wheeler is Senior Data Architect at iovation and an associate at PGExperts. He is responsible, among other things, for PGXN, pgTAP, DesignScene, and way too many CPAN modules. He lives in Portland unless he’s traveling with his family.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.