When rolling back migresia lists all migrations, then executes down in those of which timestamp is higher than the specific timestamp to rollback to. This doesn't take into account schema_migrations table, which means the same migration can be rolled back multiple times. This should work similarly to up, once a migration is applied it's not taken into account when calling migrate subsequently.
When rolling back migresia lists all migrations, then executes down in those of which timestamp is higher than the specific timestamp to rollback to. This doesn't take into account schema_migrations table, which means the same migration can be rolled back multiple times. This should work similarly to up, once a migration is applied it's not taken into account when calling migrate subsequently.