laravel/laravel — Issue #249: Migration doesn't know about partially created tables
Author: ianlandsman
Created: 2012-01-19 20:54:47+00:00
State: open

If there's a DB error during a migration the table will have been created, but not registered (apparently) with the migration history. So that when rollback is issued it will rollback the migration prior. Running migration:run then leads to a table already exists error on the migration which wasn't completed due to a database error.

In this case I was using sqlite and got this error:
http://paste.laravel.com/aS

That lead to me rolling back and then running and getting:
http://paste.laravel.com/aT