6 commits

Author	SHA1	Message	Date
Matt Button	9e6cfc6a59	Fixed a few bugs and added sensible funtionality: ... * Fixed a bug where already appled migrations would be selected when asked to bring a location up to latest version * You can now use booleans to get migrations needed to migrate to one of two extremes (TRUE = latest, FALSE = undo everything) * If you're rolling back to a version then you don't want to execute the down() for that migration	2010-12-28 03:29:57 +00:00
Matt Button	8cadcbf309	Renaming 'module' to 'location' in migration related code, makes more sense	2010-12-28 02:47:49 +00:00
Matt Button	9b0e6d7555	Updated one of the comments in the migrations model	2010-12-25 03:21:43 +00:00
Matt Button	99046c117e	Noticed a couple of bugs with query generation in the migration model, namely: ... * Migrations were only being fetched when target explicitly defined * Results weren't being ordered properly * There was no way to tell the calling code which method (i.e. up / down) should be called on migrations	2010-12-25 03:16:50 +00:00
Matt Button	afe039fb4e	Fixed a bug in the migration model where migrations that hadn't already ... been applied would be selected during rollback.	2010-12-25 03:00:34 +00:00
Matt Button	76b0533072	Added migrations model for interacting with data in migrations table ... Can currently * Get all migrations * Fetch the current version for each "module" * Get a list of migrations that need to be run to bring the db up to date	2010-12-25 02:52:51 +00:00