@rgarcia thanks! @fudanchii will merge on your approval

Yeah, we should do this.
At first I was thinking not to suppress create table error, but I think it's a moot now since the error certainly hinder full-backward compatibility with tables which exist pre-migration. Also because Migration.up and Migration.down suppressed any error at migration step and replace it with Tx.Rollback, as mentioned by @rgarcia at #226. I think I missed this one since I ever experiment to bail out at migration step error:

if err := rev.Up(mg); err != nil {
                log.Printf("Failed to upgrade to Revision Number %v\n", current)
                log.Println(err)
                // suppress any possible error from tx.Rollback
                tx.Rollback()
                return err
}

But then I revert this and going with the old behavior, since this is will useful only if we extract the migration system from the main app (standalone application to do migration solely).

This could be merged in, I will fix mysql to adapt this. Thanks.