www.talios.com

Half way through last year I came up with a simple 'framework' for handling automated database migrations, I've been using this in one project at ${work} for the last year and its worked wonders, for both production deployments and repeatable unit te

ne thing I've often found plaguing software updates during infrequent or less-than-trivial deploys is that invariably a small, but important schema change gets lost, run out of order, or skipped entirely.

This morning I was thinking about database migration issues - maintaining update scripts, rolling back development databases etc. etc.Whilst it's no major issue to keep a dump of a database around to restore to a known state and test your update scri