From 765dcc8bac9a3e3944ac6f03a6e735fdbb086f80 Mon Sep 17 00:00:00 2001 From: Taylor Otwell Date: Sun, 22 Jan 2012 15:30:02 -0600 Subject: [PATCH] tweaking the migrator. --- laravel/cli/tasks/migrate/migrator.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/laravel/cli/tasks/migrate/migrator.php b/laravel/cli/tasks/migrate/migrator.php index 7d404d55..b708a55b 100644 --- a/laravel/cli/tasks/migrate/migrator.php +++ b/laravel/cli/tasks/migrate/migrator.php @@ -78,7 +78,7 @@ public function migrate($bundle = null, $version = null) // We need to grab the latest batch ID and increment it // by one. This allows us to group the migrations such // that we can easily determine which migrations need - // to be rolled back for a given command. + // to roll back for the command. $batch = $this->database->batch() + 1; foreach ($migrations as $migration) @@ -89,7 +89,7 @@ public function migrate($bundle = null, $version = null) // After running a migration, we log its execution in the // migration table so that we can easily determine which - // migrations we will need to reverse on a rollback. + // migrations we'll reverse on a rollback. $this->database->log($migration['bundle'], $migration['name'], $batch); } } @@ -124,7 +124,7 @@ public function rollback($arguments = array()) // By only removing the migration after it has successfully rolled back, // we can re-run the rollback command in the event of any errors with // the migration. When we re-run, only the migrations that have not - // been rolled-back for the batch will still be in the database. + // been rolled back for the batch will still be in the database. $this->database->delete($migration['bundle'], $migration['name']); }