* 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
* 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
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