I did this because it was annoying that it was throwing an exception about Nil not have a down() method when I would try and rollback when there is nothing left to rollback.
It is much easier when you just cd into the directory and it setups the ruby version and the gemset that you are developing in. Plus, if the developer isn't using rvm then it doesn't do anything.
I did this because it was using it some places and not others which was causing problems when the user has a version represented as a string in some places. Plus, consistency is good, ;-)
* 'stable' of github.com:brewster/shearwater: Cleaned up == nil to .nil? Made cql last_migration func ignore "range ghosts"
Handle range ghosts in cql backend
I did this because when you have your Cassandra schema_migrations column family setup as follows you end up still getting "range ghosts". This was breaking the last_migration method in such a way that I was always getting a migration that I had previously rollback and was now a "range ghost" as the last_migration result. CREATE COLUMNFAMILY schema_migrations (version int PRIMARY KEY, migrated_at timestamp)
Some dumb bundler issue